From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH wireless v2] wifi: rework MAINTAINERS entries a bit
Date: Wed, 26 Mar 2025 08:49:25 -0700 [thread overview]
Message-ID: <085bfa6c-cad5-43cf-9432-811b744da506@oss.qualcomm.com> (raw)
In-Reply-To: <20250306092831.f7fdfe7df7b2.I7c86da443038af32e9bcbaa5f53b1e4128a0d1f9@changeid>
On 3/6/2025 12:28 AM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Since I really don't want to be CC'ed on every patch
> add X: entries for all the drivers that are otherwise
> covered. In some cases, add a bit more to drivers that
> have other entries, mostly for the vendor directories,
> but for libertas also add libertas_tf.
>
> While at it, also add all nl80211-related (vendor)
> UAPI header files to the nl80211 entry.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Johannes,
This patch has the unfortunate side-effect that get_maintainer.pl (and b4) no
longer add linux-wireless to ath* patches, and hence they no longer show up in
https://patchwork.kernel.org/project/linux-wireless/list/.
Thoughts on how to handle this?
/jeff
next prev parent reply other threads:[~2025-03-26 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 8:28 [PATCH wireless v2] wifi: rework MAINTAINERS entries a bit Johannes Berg
2025-03-26 15:49 ` Jeff Johnson [this message]
2025-03-26 15:55 ` Johannes Berg
2025-03-26 16:45 ` Jeff Johnson
2025-03-26 16:46 ` Johannes Berg
2025-03-26 17:40 ` Jeff Johnson
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=085bfa6c-cad5-43cf-9432-811b744da506@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=johan+linaro@kernel.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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