From: Kalle Valo <kvalo@kernel.org>
To: Randy Dunlap <rdunlap@infradead.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
Subject: Re: [PATCH] ath11k (gcc13): synchronize ath11k_mac_he_gi_to_nl80211_he_gi()'s return type
Date: Thu, 03 Nov 2022 08:20:00 +0200 [thread overview]
Message-ID: <87cza4ftkf.fsf@kernel.org> (raw)
In-Reply-To: <1041acdb-2978-7413-5567-ae9c14471605@infradead.org> (Randy Dunlap's message of "Tue, 1 Nov 2022 10:54:11 -0700")
Randy Dunlap <rdunlap@infradead.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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Randy Dunlap <rdunlap@infradead.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
Subject: Re: [PATCH] ath11k (gcc13): synchronize ath11k_mac_he_gi_to_nl80211_he_gi()'s return type
Date: Thu, 03 Nov 2022 08:20:00 +0200 [thread overview]
Message-ID: <87cza4ftkf.fsf@kernel.org> (raw)
In-Reply-To: <1041acdb-2978-7413-5567-ae9c14471605@infradead.org> (Randy Dunlap's message of "Tue, 1 Nov 2022 10:54:11 -0700")
Randy Dunlap <rdunlap@infradead.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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-11-03 6:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:43 [PATCH] ath11k (gcc13): synchronize ath11k_mac_he_gi_to_nl80211_he_gi()'s return type Jiri Slaby (SUSE)
2022-10-31 11:43 ` Jiri Slaby (SUSE)
2022-10-31 21:16 ` Jeff Johnson
2022-10-31 21:16 ` Jeff Johnson
2022-11-01 5:49 ` Jiri Slaby
2022-11-01 5:49 ` Jiri Slaby
2022-11-01 8:45 ` Kalle Valo
2022-11-01 8:45 ` Kalle Valo
2022-11-01 14:54 ` Randy Dunlap
2022-11-01 14:54 ` Randy Dunlap
2022-11-01 17:19 ` Kalle Valo
2022-11-01 17:19 ` Kalle Valo
2022-11-01 17:54 ` Randy Dunlap
2022-11-01 17:54 ` Randy Dunlap
2022-11-03 6:20 ` Kalle Valo [this message]
2022-11-03 6:20 ` Kalle Valo
2022-11-03 6:21 ` Randy Dunlap
2022-11-03 6:21 ` Randy Dunlap
2022-11-02 6:18 ` Jiri Slaby
2022-11-02 6:18 ` Jiri Slaby
2022-11-02 16:52 ` Kalle Valo
2022-11-02 16:52 ` 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=87cza4ftkf.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mliska@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.com \
--cc=rdunlap@infradead.org \
/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.