netdev - Re: pull-request: wireless-next-2024-09-11

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: <878qvxfkso.fsf@kernel.org>
Date: Thu, 12 Sep 2024 09:28:07 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Ping-Ke Shih <pkshih@...ltek.com>
Cc: Jakub Kicinski <kuba@...nel.org>,  "netdev@...r.kernel.org"
 <netdev@...r.kernel.org>,  "linux-wireless@...r.kernel.org"
 <linux-wireless@...r.kernel.org>
Subject: Re: pull-request: wireless-next-2024-09-11

Ping-Ke Shih <pkshih@...ltek.com> writes:

> Jakub Kicinski <kuba@...nel.org> wrote:
>> On Wed, 11 Sep 2024 15:36:33 -0700 Jakub Kicinski wrote:
>> > > What's the deadline for these? Do you need the fixes tomorrow or can it
>> > > wait a week or two?
>> >
>> > It can wait, half of them are old anyway
>> 
>> Oh, that's because they are in staging :) I missed that.
>> But anyway, I don't think that a harmless, single compiler,
>> W=1 warning is a blocker.

Ok, we'll send the rtw89 fix in the normal wireless pull request,
hopefully before the merge window closes.

> I have fixed warnings of "wifi: rtw89" by [1]. For staging code, I use another
> patchset [2] to fix it.

Oh wow, that was quick. We have 24/7 watch around the world :) Thanks Ping!

> I'm not sure [1] should go wireless or rtw tree. Please guide me. Thanks. 

Let's queue the rtw89 fix for wireless so that the quick goes to net
tree soon. So please assign it to me on patchwork.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches