From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] wifi: free SKBTX_WIFI_STATUS skb tx_flags flag
Date: Mon, 24 Mar 2025 09:12:19 -0700 [thread overview]
Message-ID: <20250324091219.235ca852@kernel.org> (raw)
In-Reply-To: <e0ac6ed58b71f0293ec576b45c8e2645c0695d52.camel@sipsolutions.net>
On Mon, 24 Mar 2025 16:57:52 +0100 Johannes Berg wrote:
> On Mon, 2025-03-24 at 08:53 -0700, Jakub Kicinski wrote:
> > On Thu, 13 Mar 2025 13:49:39 +0100 Johannes Berg wrote:
> > > Someone mentioned today at netdevconf that we've run out of
> >
> > Don't recall the mention, but I'd guess maybe Jason Xing during
> > his timestamping talk? Change itself LGTM!
>
> Yeah, I think so. Timing would be right too, his talk was around noon
> that day :)
>
> I guess I can merge it through wireless for 6.16, unless you have any
> concerns? I can also resend it for net-next after the merge window
> closes, the wireless drivers/stack changes are almost certainly not
> going to have any conflicts, but overall it's trivial anyway.
6.16 makes sense; no preference on the tree, whichever's easier.
next prev parent reply other threads:[~2025-03-24 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 12:49 [RFC PATCH] wifi: free SKBTX_WIFI_STATUS skb tx_flags flag Johannes Berg
2025-03-24 15:53 ` Jakub Kicinski
2025-03-24 15:57 ` Johannes Berg
2025-03-24 16:12 ` Jakub Kicinski [this message]
2025-03-24 16:33 ` Jason Xing
2025-03-24 16:53 ` Jason Xing
2025-03-24 16:56 ` Johannes Berg
2025-03-24 16:59 ` Jason Xing
2025-04-26 23:55 ` Jason Xing
2025-04-28 7:41 ` Johannes Berg
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=20250324091219.235ca852@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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.