netdev - Re: [RFC PATCH] wifi: free SKBTX_WIFI_STATUS skb tx

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250324091219.235ca852@kernel.org>
Date: Mon, 24 Mar 2025 09:12:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Johannes Berg <johannes@...solutions.net>
Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] wifi: free SKBTX_WIFI_STATUS skb tx_flags flag

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.