Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <1041acdb-2978-7413-5567-ae9c14471605@infradead.org>
Date:   Tue, 1 Nov 2022 10:54:11 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.0
Subject: Re: [PATCH] ath11k (gcc13): synchronize
 ath11k_mac_he_gi_to_nl80211_he_gi()'s return type
Content-Language: en-US
To:     Kalle Valo <kvalo@kernel.org>
Cc:     Jiri Slaby <jirislaby@kernel.org>,
        Jeff Johnson <quic_jjohnson@quicinc.com>,
        linux-kernel@vger.kernel.org, Martin Liska <mliska@suse.cz>,
        "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>, ath11k@lists.infradead.org,
        linux-wireless@vger.kernel.org, netdev@vger.kernel.org
References: <20221031114341.10377-1-jirislaby@kernel.org>
 <55c4d139-0f22-e7ba-398a-e3e0d8919220@quicinc.com>
 <833c7f2f-c140-5a0b-1efc-b858348206ec@kernel.org> <87bkprgj0b.fsf@kernel.org>
 <503a3b36-2256-a9ce-cffe-5c0ed51f6f62@infradead.org>
 <87tu3ifv8z.fsf@kernel.org>
From:   Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <87tu3ifv8z.fsf@kernel.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi--

On 11/1/22 10:19, Kalle Valo wrote:
> Randy Dunlap <rdunlap@infradead.org> writes:
> 
>> On 11/1/22 01:45, Kalle Valo wrote:
>>> Jiri Slaby <jirislaby@kernel.org> writes:
>>>
>>>> On 31. 10. 22, 22:16, Jeff Johnson wrote:
>>>>
>>>>> On 10/31/2022 4:43 AM, Jiri Slaby (SUSE) wrote:
>>
>>>>> Suggest the subject should be
>>>>> wifi: ath11k: synchronize ath11k_mac_he_gi_to_nl80211_he_gi()'s return type
>>>>
>>>> FWIW I copied from:
>>>> $ git log --format=%s  drivers/net/wireless/ath/ath11k/mac.h
>>>> ath11k: Handle keepalive during WoWLAN suspend and resume
>>>> ath11k: reduce the wait time of 11d scan and hw scan while add interface
>>>> ath11k: Add basic WoW functionalities
>>>> ath11k: add support for hardware rfkill for QCA6390
>>>> ath11k: report tx bitrate for iw wlan station dump
>>>> ath11k: add 11d scan offload support
>>>> ath11k: fix read fail for htt_stats and htt_peer_stats for single pdev
>>>> ath11k: add support for BSS color change
>>>> ath11k: add support for 80P80 and 160 MHz bandwidth
>>>> ath11k: Add support for STA to handle beacon miss
>>>> ath11k: add support to configure spatial reuse parameter set
>>>> ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references
>>>> ath11k: Perform per-msdu rx processing
>>>> ath11k: fix incorrect peer stats counters update
>>>> ath11k: Move mac80211 hw allocation before wmi_init command
>>>> ath11k: fix missed bw conversion in tx completion
>>>> ath11k: driver for Qualcomm IEEE 802.11ax devices
>>>
>>> Yeah, using "wifi:" is a new prefix we started using with wireless
>>> patches this year.
>>>
>>
>> It would be nice if that was documented somewhere...
> 
> It is mentioned on our wiki but I doubt anyone reads it :)

I think that you are correct. ;)

> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#subject
> 
> Do let me know if there are other places which should have this info.

Ideally it would be in the subsystem's profile document as described in the
MAINTAINERS file:

	P: Subsystem Profile document for more details submitting
	   patches to the given subsystem. This is either an in-tree file,
	   or a URI. See Documentation/maintainer/maintainer-entry-profile.rst
	   for details.

although that seems to be overkill IMHO just to add a prefix: setting.

You could just clone some other maintainer's Profile document and then modify it
to anything that you would like to have in it as far as Maintaining and patching
are concerned.

> I did assume it will take at least a year or two before people get used
> to the new prefix, but my patchwork script has a check for this and it's
> trivial to fix the subject before I commit the patch. So hopefully the
> switch goes smoothly.

OK.

Thanks.

-- 
~Randy