linux-kernel - Re: [PATCH 0/3] wifi: brcm80211: Deadcoding around phy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3cfa6ddfb5493aff609c5a51c84d61a7ed36d13f.camel@sipsolutions.net>
Date: Mon, 30 Jun 2025 14:12:02 +0200
From: Johannes Berg <johannes@...solutions.net>
To: "Dr. David Alan Gilbert" <linux@...blig.org>
Cc: arend.vanspriel@...adcom.com, kvalo@...nel.org, 
	linux-wireless@...r.kernel.org, brcm80211@...ts.linux.dev, 
	brcm80211-dev-list.pdl@...adcom.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn

Hi,

> > 2) it'd help for the automatic bot runs etc. to have, in the subject,
> >    '[PATCH wireless-next]' (or perhaps rtw-next etc.)
> 
> Oh right; that wasn't too obvious to me because get_maintainer has
> linux-wireless@ in the list but also had the brcm80211 - so I
> didn't know if this went through brcm or wireless picked it up.
> And what's rtw ?

Hmm, right, brcm80211 does have a separate list but patches still flow
only via the wireless list.

Currently, we have:
ath/ath-next - Qualcomm drivers
rtw/rtw-next - Realtek drivers
iwlwifi-fixes/iwlwifi-next - Intel iwlwifi driver
mt76 - Mediatek drivers
wireless / wireless-next - catch-all for everything else

> (Perhaps a Documenation/process/maintainer-wireless.rst would be good? )

Yeah, perhaps, though it's kind of difficult to really pin down the
exact list, it has been changing a bit.

TBH, wireless / wireless-next is mostly just fine anyway. Only if
something depends on other work in the specific trees would the other
tags really be needed, i.e. for people who work on it more actively.
With wireless / wireless-next the bot will still build-test it etc.,
whereas without a tag it may never do that at all.

johannes