From: Jiri Slaby <jirislaby@kernel.org>
To: Kalle Valo <kvalo@kernel.org>, Randy Dunlap <rdunlap@infradead.org>
Cc: 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: Wed, 2 Nov 2022 07:18:00 +0100 [thread overview]
Message-ID: <eeac01aa-5c3d-da4f-3acb-0698de23b2b4@kernel.org> (raw)
In-Reply-To: <87tu3ifv8z.fsf@kernel.org>
On 01. 11. 22, 18:19, Kalle Valo wrote:
> 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.
I think so. It will take some turnarounds for you before this starts
appearing in git log output for every wireless driver. Then, people will
start picking the prefix up from there ;).
thanks,
--
js
suse labs
next prev parent reply other threads:[~2022-11-02 6:18 UTC|newest]
Thread overview: 11+ 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 21:16 ` Jeff Johnson
2022-11-01 5:49 ` Jiri Slaby
2022-11-01 8:45 ` Kalle Valo
2022-11-01 14:54 ` Randy Dunlap
2022-11-01 17:19 ` Kalle Valo
2022-11-01 17:54 ` Randy Dunlap
2022-11-03 6:20 ` Kalle Valo
2022-11-03 6:21 ` Randy Dunlap
2022-11-02 6:18 ` Jiri Slaby [this message]
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=eeac01aa-5c3d-da4f-3acb-0698de23b2b4@kernel.org \
--to=jirislaby@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).