From: Martin Schiller <ms@dev.tdt.de>
To: Xie He <xie.he.0141@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Hendry <andrew.hendry@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH net-next RFC] MAINTAINERS: Add Martin Schiller as a maintainer for the X.25 stack
Date: Thu, 12 Nov 2020 08:06:37 +0100 [thread overview]
Message-ID: <7baa879ed48465e7af27d4cbbe41c3e6@dev.tdt.de> (raw)
In-Reply-To: <20201111213608.27846-1-xie.he.0141@gmail.com>
On 2020-11-11 22:36, Xie He wrote:
> Hi Martin Schiller, would you like to be a maintainer for the X.25
> stack?
>
> As we know the linux-x25 mail list has stopped working for a long time.
> Adding you as a maintainer may make you be Cc'd for new patches so that
> you can review them.
About 1 year ago I was asked by Arnd Bergmann if I would like to become
the maintainer for the X.25 stack:
https://patchwork.ozlabs.org/project/netdev/patch/20191209151256.2497534-4-arnd@arndb.de/#2320767
Yes, I would agree to be listed as a maintainer.
But I still think it is important that we either repair or delete the
linux-x25 mailing list. The current state that the messages are going
into nirvana is very unpleasant.
>
> The original maintainer of X.25 network layer (Andrew Hendry) has
> stopped
> sending emails to the netdev mail list since 2013. So there is
> practically
> no maintainer for X.25 code currently.
>
> Cc: Martin Schiller <ms@dev.tdt.de>
> Cc: Andrew Hendry <andrew.hendry@gmail.com>
> Signed-off-by: Xie He <xie.he.0141@gmail.com>
> ---
> MAINTAINERS | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2a0fde12b650..9ebcb0708d5d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9832,13 +9832,6 @@ S: Maintained
> F: arch/mips/lantiq
> F: drivers/soc/lantiq
>
> -LAPB module
> -L: linux-x25@vger.kernel.org
> -S: Orphan
> -F: Documentation/networking/lapb-module.rst
> -F: include/*/lapb.h
> -F: net/lapb/
> -
> LASI 53c700 driver for PARISC
> M: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
> L: linux-scsi@vger.kernel.org
> @@ -18979,12 +18972,19 @@ L: linux-kernel@vger.kernel.org
> S: Maintained
> N: axp[128]
>
> -X.25 NETWORK LAYER
> -M: Andrew Hendry <andrew.hendry@gmail.com>
> +X.25 STACK
> +M: Martin Schiller <ms@dev.tdt.de>
> L: linux-x25@vger.kernel.org
> -S: Odd Fixes
> +L: netdev@vger.kernel.org
> +S: Maintained
> +F: Documentation/networking/lapb-module.txt
> F: Documentation/networking/x25*
> +F: drivers/net/wan/hdlc_x25.c
> +F: drivers/net/wan/lapbether.c
> +F: include/*/lapb.h
> F: include/net/x25*
> +F: include/uapi/linux/x25.h
> +F: net/lapb/
> F: net/x25/
>
> X86 ARCHITECTURE (32-BIT AND 64-BIT)
next prev parent reply other threads:[~2020-11-12 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 21:36 [PATCH net-next RFC] MAINTAINERS: Add Martin Schiller as a maintainer for the X.25 stack Xie He
2020-11-12 7:06 ` Martin Schiller [this message]
2020-11-12 8:14 ` Xie He
2020-11-12 16:31 ` Jakub Kicinski
2023-08-01 11:09 ` Joel Granados
2023-08-01 11:16 ` Martin Schiller
2023-08-01 12:29 ` Joel Granados
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=7baa879ed48465e7af27d4cbbe41c3e6@dev.tdt.de \
--to=ms@dev.tdt.de \
--cc=andrew.hendry@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xie.he.0141@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).