From: Xie He <xie.he.0141@gmail.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Network Development <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux X25 <linux-x25@vger.kernel.org>,
Martin Schiller <ms@dev.tdt.de>,
Andrew Hendry <andrew.hendry@gmail.com>
Subject: Re: [PATCH net] drivers/net/wan/x25_asy: Added needed_headroom and a skb->len check
Date: Tue, 11 Aug 2020 19:26:32 -0700 [thread overview]
Message-ID: <CAJht_EMyp5iXyGWVse7sqW0MDJ3iLH5cDcbGm1yyXt+07x9Naw@mail.gmail.com> (raw)
In-Reply-To: <CA+FuTSfS1XX9ag6npPM95Tiu_hhuan+Foxe1B+_66M-cf+26UA@mail.gmail.com>
On Tue, Aug 11, 2020 at 3:50 AM Willem de Bruijn
<willemdebruijn.kernel@gmail.com> wrote:
>
> > I became interested in X.25 when I was trying different address
> > families that Linux supported. I tried AF_X25 sockets. And then I
> > tried to use the X.25 link layer directly through AF_PACKET. I believe
> > both AF_X25 sockets and AF_PACKET sockets need to work without
> > problems with X.25 drivers - lapbether and x25_asy. There is another
> > X.25 driver (hdlc_x25) in the kernel. I haven't been able to run that
> > driver. But that driver seems to be the real driver which is really
> > used, and I know Martin Schiller <ms@dev.tdt.de> is an active user and
> > developer of that driver.
>
> Great, sounds like we might have additional LAPB and X25 maintainers soon? :)
:) I just want to fix any problems I see. I'll do this whenever I have time.
> MAINTAINERS lists Andrew Hendry as maintainer for X.25. Please do CC them.
OK. I'll surely do that. Thanks!
next prev parent reply other threads:[~2020-08-12 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 2:35 [PATCH net] drivers/net/wan/x25_asy: Added needed_headroom and a skb->len check Xie He
2020-08-09 9:12 ` Willem de Bruijn
2020-08-09 18:08 ` Xie He
2020-08-10 7:20 ` Willem de Bruijn
2020-08-10 19:50 ` Xie He
2020-08-11 10:50 ` Willem de Bruijn
2020-08-12 2:26 ` Xie He [this message]
2020-08-11 17:32 ` David Miller
2020-08-12 2:30 ` Xie He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJht_EMyp5iXyGWVse7sqW0MDJ3iLH5cDcbGm1yyXt+07x9Naw@mail.gmail.com \
--to=xie.he.0141@gmail.com \
--cc=andrew.hendry@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).