From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: arend.vanspriel@broadcom.com, kvalo@kernel.org,
linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn
Date: Fri, 27 Jun 2025 17:51:57 +0000 [thread overview]
Message-ID: <aF7aPZc3xXfcc-UR@gallifrey> (raw)
In-Reply-To: <7625f178e7c2be9fd11f1b4cdeb4da47a4635c93.camel@sipsolutions.net>
* Johannes Berg (johannes@sipsolutions.net) wrote:
> Hi,
Hi Johannes,
> Just a couple of general comments for the future:
>
> 1) you can drop Kalle, he hasn't been involved for a while now
Oh yeh, I forgot about that.
> 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 ?
(Perhaps a Documenation/process/maintainer-wireless.rst would be good? )
Thanks again,
Dave
> Thanks,
> johannes
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-06-27 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:08 [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn linux
2025-06-26 14:08 ` [PATCH 1/3] wifi: brcm80211: Remove unused functions linux
2025-07-23 11:12 ` Arend van Spriel
2025-06-26 14:08 ` [PATCH 2/3] wifi: brcm80211: Remove more " linux
2025-07-23 11:13 ` Arend van Spriel
2025-06-26 14:08 ` [PATCH 3/3] wifi: brcm80211: Remove yet " linux
2025-07-23 11:13 ` Arend van Spriel
2025-06-27 7:11 ` [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn Johannes Berg
2025-06-27 17:51 ` Dr. David Alan Gilbert [this message]
2025-06-30 12:12 ` Johannes Berg
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=aF7aPZc3xXfcc-UR@gallifrey \
--to=linux@treblig.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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