Johannes Berg <johan...@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
