From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH wireless v2] wifi: rework MAINTAINERS entries a bit
Date: Wed, 26 Mar 2025 09:45:38 -0700 [thread overview]
Message-ID: <f703bb34-45f8-4f8b-b940-72428efa3c46@oss.qualcomm.com> (raw)
In-Reply-To: <6ef5049a68157bae0e121f48afc1d872a25087f7.camel@sipsolutions.net>
On 3/26/2025 8:55 AM, Johannes Berg wrote:
> On Wed, 2025-03-26 at 08:49 -0700, Jeff Johnson wrote:
>>
>> 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/.
>>
>
> Oops. I _wanted_ that entry to no longer match so I don't get CC'ed on
> everything ... I guess we need to add L: entries to all the things I
> X:'ed. I sort of thought that might be there anyway, but I see that's
> not the case for everything ... below change perhaps?
>
> johannes
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d19627afa652..09bd9827f318 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3655,11 +3655,11 @@ T: git git://github.com/AlbanBedel/linux
> F: Documentation/devicetree/bindings/phy/phy-ath79-usb.txt
> F: drivers/phy/qualcomm/phy-ath79-usb.c
>
> -ATHEROS ATH GENERIC UTILITIES
> +ATHEROS ATH WIRELESS UTILITIES AND DRIVERS
> M: Jeff Johnson <jjohnson@kernel.org>
> L: linux-wireless@vger.kernel.org
> S: Supported
> -F: drivers/net/wireless/ath/*
> +F: drivers/net/wireless/ath/
unfortunately the ath* specific entries will override so I think we need:
diff --git a/MAINTAINERS b/MAINTAINERS
index 6191b699352e..927d92518fbb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19387,6 +19387,7 @@ F: drivers/media/tuners/qt1010*
QUALCOMM ATH12K WIRELESS DRIVER
M: Jeff Johnson <jjohnson@kernel.org>
L: ath12k@lists.infradead.org
+L: linux-wireless@vger.kernel.org
S: Supported
W: https://wireless.wiki.kernel.org/en/users/Drivers/ath12k
T: git git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
@@ -19396,6 +19397,7 @@ N: ath12k
QUALCOMM ATHEROS ATH10K WIRELESS DRIVER
M: Jeff Johnson <jjohnson@kernel.org>
L: ath10k@lists.infradead.org
+L: linux-wireless@vger.kernel.org
S: Supported
W: https://wireless.wiki.kernel.org/en/users/Drivers/ath10k
T: git git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
@@ -19405,6 +19407,7 @@ N: ath10k
QUALCOMM ATHEROS ATH11K WIRELESS DRIVER
M: Jeff Johnson <jjohnson@kernel.org>
L: ath11k@lists.infradead.org
+L: linux-wireless@vger.kernel.org
S: Supported
W: https://wireless.wiki.kernel.org/en/users/Drivers/ath11k
B: https://wireless.wiki.kernel.org/en/users/Drivers/ath11k/bugreport
next prev parent reply other threads:[~2025-03-26 16:45 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
2025-03-26 15:55 ` Johannes Berg
2025-03-26 16:45 ` Jeff Johnson [this message]
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=f703bb34-45f8-4f8b-b940-72428efa3c46@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=johan+linaro@kernel.org \
--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