From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Rafał Miłecki" <rafal@milecki.pl>, linux-wireless@vger.kernel.org
Subject: Re: wiki: tree labels in patches
Date: Fri, 16 Nov 2018 10:54:38 +0200 [thread overview]
Message-ID: <87efbl8ks1.fsf@codeaurora.org> (raw)
In-Reply-To: <c66fa62a88f1d99dc35019c5e7d00b062c6b1785.camel@sipsolutions.net> (Johannes Berg's message of "Fri, 16 Nov 2018 09:49:26 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Fri, 2018-11-16 at 10:46 +0200, Kalle Valo wrote:
>
>> Yes, I do see your FIX tag in patchwork:
>>
>> [ 31] [FIX] brcmfmac: fix reporting support for 160 MHz channels 2018-11-08
>>
>> But "FIX" is a bit ambigous as not all fixes not go to wireless-drivers,
>> they can also go to wireless-drivers-next. So I prefer using the release
>> number (or name of the tree) like this:
>>
>> [PATCH 4.20] brcmfmac: fix reporting support for 160 MHz channels
>
> FWIW, davem/networking just use
>
> [PATCH net]
> [PATCH net-next]
>
> which puts a bit more effort on the submitter but is a bit easier on the
> maintainer I suppose. Also, not really a problem here, but it would help
> disambiguate different trees on the same mailing list. I don't really
> mind either way.
Actually I already added that to the wiki[1] but made it optional just
bacause it's harder for patch submitters who are not so familiar with
our tree structure. But yes, I also like using the full tree name as the
label, even more so as it would help me to automatically assign patches
to correct maintainers in patchwork.
[1] https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#tree_labels
--
Kalle Valo
next prev parent reply other threads:[~2018-11-16 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 15:08 [PATCH FIX] brcmfmac: fix reporting support for 160 MHz channels Rafał Miłecki
2018-11-09 14:05 ` Kalle Valo
2018-11-09 20:10 ` Rafał Miłecki
2018-11-16 8:40 ` Kalle Valo
2018-11-16 8:46 ` wiki: tree labels in patches Kalle Valo
2018-11-16 8:49 ` Johannes Berg
2018-11-16 8:54 ` Kalle Valo [this message]
2018-11-16 8:55 ` Rafał Miłecki
2018-11-16 13:13 ` [PATCH FIX] brcmfmac: fix reporting support for 160 MHz channels Kalle Valo
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=87efbl8ks1.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rafal@milecki.pl \
/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.