From: "Tiwei Bie" <tiwei.btw@antgroup.com>
To: Lukas Bulwahn <lbulwahn@redhat.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-um@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: remove obsolete file entry in TUN/TAP DRIVER
Date: Wed, 07 May 2025 19:52:22 +0800 [thread overview]
Message-ID: <2ac70b02-7841-4355-ae71-5b57a6ce15e2@antgroup.com> (raw)
In-Reply-To: <20250507071004.35120-1-lukas.bulwahn@redhat.com>
On 2025/5/7 15:10, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit 65eaac591b75 ("um: Remove obsolete legacy network transports")
> removes the directory arch/um/os-Linux/drivers/, but misses to remove the
> file entry in TUN/TAP DRIVER referring to that directory.
>
> Remove this obsolete file entry. While at it, put the section name in
> capital letters.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> ---
> MAINTAINERS | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9c166503cc6b..34a55e3ff863 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -24981,13 +24981,12 @@ L: linux-parisc@vger.kernel.org
> S: Orphan
> F: drivers/net/ethernet/dec/tulip/
>
> -TUN/TAP driver
> +TUN/TAP DRIVER
> M: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
> M: Jason Wang <jasowang@redhat.com>
> S: Maintained
> W: http://vtun.sourceforge.net/tun
> F: Documentation/networking/tuntap.rst
> -F: arch/um/os-Linux/drivers/
> F: drivers/net/tap.c
> F: drivers/net/tun*
>
I missed that. Thanks for the fix!
Reviewed-by: Tiwei Bie <tiwei.btw@antgroup.com>
Regards,
Tiwei
prev parent reply other threads:[~2025-05-07 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 7:10 [PATCH] MAINTAINERS: remove obsolete file entry in TUN/TAP DRIVER Lukas Bulwahn
2025-05-07 11:52 ` Tiwei Bie [this message]
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=2ac70b02-7841-4355-ae71-5b57a6ce15e2@antgroup.com \
--to=tiwei.btw@antgroup.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lukas.bulwahn@redhat.com \
--cc=richard@nod.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).