netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH RFC net 1/2] MAINTAINERS: consistently exclude wireless files from NETWORKING [GENERAL]
Date: Mon, 7 Oct 2024 15:13:05 +0100	[thread overview]
Message-ID: <20241007141305.GD32733@kernel.org> (raw)
In-Reply-To: <87setb7us5.fsf@kernel.org>

On Fri, Oct 04, 2024 at 06:27:38PM +0300, Kalle Valo wrote:
> Simon Horman <horms@kernel.org> writes:
> 
> > We already exclude wireless drivers from the netdev@ traffic, to
> > delegate it to linux-wireless@, and avoid overwhelming netdev@.
> >
> > Many of the following wireless-related sections MAINTAINERS
> > are already not included in the NETWORKING [GENERAL] section.
> > For consistency, exclude those that are.
> >
> > * 802.11 (including CFG80211/NL80211)
> > * MAC80211
> > * RFKILL
> >
> > Signed-off-by: Simon Horman <horms@kernel.org>
> > ---
> >  MAINTAINERS | 11 +++++++++++
> >  1 file changed, 11 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index c27f3190737f..ea3ea2c0d3fa 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -16197,8 +16197,19 @@ F:	lib/random32.c
> >  F:	net/
> >  F:	tools/net/
> >  F:	tools/testing/selftests/net/
> > +X:	Documentation/networking/mac80211-injection.rst
> > +X:	Documentation/networking/mac80211_hwsim/
> > +X:	Documentation/networking/regulatory.rst
> > +X:	include/net/cfg80211.h
> > +X:	include/net/ieee80211_radiotap.h
> > +X:	include/net/iw_handler.h
> > +X:	include/net/mac80211.h
> > +X:	include/net/wext.h
> 
> Should we add also lib80211.h?

Thanks, I missed that one. Perhaps it should have:

* An F: entry in the MAC80211
* An X: entry in the NETWORKING [GENERAL]

If so, perhaps I can just add that to a v2 of this patch.
Let me know what you think.

  reply	other threads:[~2024-10-07 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 10:03 [PATCH RFC net 0/2] MAINTAINERS: Networking file coverage updates Simon Horman
2024-10-04 10:03 ` [PATCH RFC net 1/2] MAINTAINERS: consistently exclude wireless files from NETWORKING [GENERAL] Simon Horman
2024-10-04 14:32   ` Johannes Berg
2024-10-04 15:27   ` Kalle Valo
2024-10-07 14:13     ` Simon Horman [this message]
2024-10-07 17:30       ` Johannes Berg
2024-10-07 17:41       ` Kalle Valo
2024-10-07 18:03         ` Johannes Berg
2024-10-09  8:43           ` Simon Horman
2024-10-04 10:03 ` [PATCH RFC net 2/2] MAINTAINERS: Add headers and mailing list to UDP section Simon Horman
2024-10-04 15:25   ` Willem de Bruijn
2024-10-04 22:42 ` [PATCH RFC net 0/2] MAINTAINERS: Networking file coverage updates Jakub Kicinski

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=20241007141305.GD32733@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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).