From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend Van Spriel <aspriel@gmail.com>,
linux-wireless@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 00/76] wifi: more MLO work
Date: Mon, 18 Jul 2022 11:51:04 +0300 [thread overview]
Message-ID: <87k08ast1j.fsf@kernel.org> (raw)
In-Reply-To: <3ac3c91120a128f66ca3806294f6a783e0f1131f.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 14 Jul 2022 10:30:19 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Thu, 2022-07-14 at 10:26 +0200, Arend Van Spriel wrote:
>>
>> Just for my own patch submit process. What is the reason I am seeing the
>> "wifi:" prefix being used with patches on linux-wireless list? Is there
>> other wireless tech used, eg. "bt:" or so?
>>
>
> Well, we had a discussion with Jakub, and he kind of indicated that he'd
> like to see a bit more generic prefixes to clarify things.
>
> We've kind of been early adopters to try it out and see what it looks
> like, he hasn't pushed it and wanted to have a discussion (e.g. at LPC
> or netdevconf) about it first, but it kind of makes sense since not
> everyone can know all the different drivers and components.
I have been supposed to document this in the wiki and announce it
properly, but as usual I was too busy before the vacation to do
anything. And now I'm on vacation and trying to enjoy the 13 C of
"warmth" here in Finland :D
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-07-18 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220713094502.163926-1-johannes@sipsolutions.net>
[not found] ` <e9ecb9c8-cb5b-d727-38d6-ef5a0bf81cef@gmail.com>
2022-07-14 8:30 ` [PATCH 00/76] wifi: more MLO work Johannes Berg
2022-07-18 8:51 ` Kalle Valo [this message]
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=87k08ast1j.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=aspriel@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).