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: <0b6a69a39d6b463da41c5a83b747e4cd@realtek.com>
Date: Thu, 12 Sep 2024 02:33:08 +0000
From: Ping-Ke Shih <pkshih@...ltek.com>
To: Jakub Kicinski <kuba@...nel.org>, Kalle Valo <kvalo@...nel.org>
CC: "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

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.

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

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

[1] https://lore.kernel.org/linux-wireless/20240912021626.10494-1-pkshih@realtek.com/T/#u
[2] https://lore.kernel.org/linux-staging/20240912022522.10715-1-pkshih@realtek.com/T/#t



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ