From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Remi Pommarel <repk@triplefau.lt>,
Johannes Berg <johannes@sipsolutions.net>
Cc: Bert Karwatzki <spasswolf@web.de>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH wireless v2 1/2] wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()
Date: Thu, 17 Jul 2025 12:42:25 -0700 [thread overview]
Message-ID: <ead8f37c-6fc3-472f-94f7-ad4ea6fa0fba@oss.qualcomm.com> (raw)
In-Reply-To: <a5e85969-1dc9-4d6b-be2e-ac2338d38d98@oss.qualcomm.com>
On 7/17/2025 8:46 AM, Jeff Johnson wrote:
> On 7/17/2025 7:22 AM, Remi Pommarel wrote:
>> For the record, if I am not mistaken, ath12k driver does not seem to
>> support 802.11 encaps HW offloading mainline yet, I do seem to have some
>> vendor patches to support it though.
>
> Upstreaming this functionality is in the internal pipeline but won't make the
> v6.17 merge window.
I make a comment like that and all of a sudden internal reviews get expedited.
s/but won't/and should/
/jeff
next prev parent reply other threads:[~2025-07-17 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 16:28 [PATCH wireless v2 0/2] Fix packets processed after vif is stopped Remi Pommarel
2025-03-24 16:28 ` [PATCH wireless v2 1/2] wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue() Remi Pommarel
2025-04-10 21:55 ` Bert Karwatzki
2025-04-11 10:06 ` Remi Pommarel
2025-04-11 11:10 ` Bert Karwatzki
2025-04-11 12:15 ` Remi Pommarel
2025-07-17 13:21 ` Remi Pommarel
2025-07-17 13:46 ` Johannes Berg
2025-07-17 14:22 ` Remi Pommarel
2025-07-17 15:46 ` Jeff Johnson
2025-07-17 19:42 ` Jeff Johnson [this message]
2025-04-11 14:16 ` Johannes Berg
2025-03-24 16:28 ` [PATCH wireless v2 2/2] wifi: mac80211: Purge vif txq in ieee80211_do_stop() Remi Pommarel
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=ead8f37c-6fc3-472f-94f7-ad4ea6fa0fba@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=repk@triplefau.lt \
--cc=spasswolf@web.de \
/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
all inboxes | Powered by JetHome®