From: Kalle Valo <kvalo@kernel.org>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
Felix Fietkau <nbd@nbd.name>,
gregory.greenman@intel.com, Ping-Ke Shih <pkshih@realtek.com>
Subject: [IMPORTANT] Use of wifi: prefix in patch titles
Date: Wed, 27 Jul 2022 13:40:23 +0300 [thread overview]
Message-ID: <87bktaq1ns.fsf@kernel.org> (raw)
Hi,
Some of you have already noticed that few weeks ago we started using
"wifi:" in patch titles, here are few examples:
wifi: mac80211: optionally implement MLO multicast TX
wifi: cfg80211: report link ID in NL80211_CMD_FRAME
wifi: wcn36xx: fix repeated words in comments
wifi: ath11k: mac: fix long line
Everyone, please start using this new prefix on all wireless patches
from now on. But no need to resend existing patches because of this.
I also updated the wiki:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Kalle
reply other threads:[~2022-07-27 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87bktaq1ns.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=pkshih@realtek.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.