DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 340C5208A3
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date:   Fri, 16 Nov 2018 09:55:12 +0100
From:   =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= <rafal@milecki.pl>
To:     Kalle Valo <kvalo@codeaurora.org>
Cc:     linux-wireless@vger.kernel.org
Subject: Re: wiki: tree labels in patches
In-Reply-To: <87in0x8l4t.fsf_-_@codeaurora.org>
References: <20181108150829.24842-1-zajec5@gmail.com>
 <87lg62cpno.fsf@codeaurora.org>
 <f1e1160ba35a42e12a0162629be23304@milecki.pl>
 <87in0x8l4t.fsf_-_@codeaurora.org>
Message-ID: <b5316181600c25788eb76f246d3482bc@milecki.pl>
User-Agent: Roundcube Webmail/1.3.8
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On 2018-11-16 09:46, Kalle Valo wrote:
> (changing subject for better visibility and trimming Cc)
> 
> Rafał Miłecki <rafal@milecki.pl> writes:
> 
>> On 2018-11-09 15:05, Kalle Valo wrote:
>>> Rafał Miłecki <zajec5@gmail.com> writes:
>>> 
>>>> From: Rafał Miłecki <rafal@milecki.pl>
>>>> 
>>>> Driver can report IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160MHZ so it's
>>>> important to provide valid & complete info about supported bands for
>>>> each channel. By default no support for 160 MHz should be assumed
>>>> unless
>>>> firmware reports it for a given channel later.
>>>> 
>>>> This fixes info passed to the userspace. Without that change 
>>>> userspace
>>>> could try to use invalid channel and fail to start an interface.
>>>> 
>>>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>>>> Cc: stable@vger.kernel.org
>>> 
>>> Should this be queued to 4.20?
>> 
>> That's my suggestion.
>> 
>> I try to mark fixes (patches for currently developed release) with an
>> extra FIX tag in a subject. Do you have any other method in mind that
>> would be preferred by you?
> 
> 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
> 
> After seeing your question I added something about this to the wiki
> which hopefully helps others:
> 
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#tree_labels

Got it, thanks!