linux-kernel - Re: [PATCH] ath11k (gcc13): synchronize ath11k_mac_he_gi_to_nl80211_he

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3efd119a-6814-7f39-3c7c-c17490adc876@infradead.org>
Date:   Wed, 2 Nov 2022 23:21:03 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Kalle Valo <kvalo@...nel.org>
Cc:     Jiri Slaby <jirislaby@...nel.org>,
        Jeff Johnson <quic_jjohnson@...cinc.com>,
        linux-kernel@...r.kernel.org, Martin Liska <mliska@...e.cz>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>, ath11k@...ts.infradead.org,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] ath11k (gcc13): synchronize
 ath11k_mac_he_gi_to_nl80211_he_gi()'s return type



On 11/2/22 23:20, Kalle Valo wrote:
> Randy Dunlap <rdunlap@...radead.org> writes:
> 
>>>>> 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.
> 
> Ah, we should add that doc for wireless. Thanks for the idea, I added
> that to my todo list.
> 

Thank you. :)

-- 
~Randy