netdev - Re: pull-request: wireless-next-2024-03-08

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

Message-ID: <a73e5a8f7f6807b736c15a3ea25d063451aec6b5.camel@realtek.com>
Date: Sat, 9 Mar 2024 00:19:46 +0000
From: Ping-Ke Shih <pkshih@...ltek.com>
To: "kvalo@...nel.org" <kvalo@...nel.org>, "kuba@...nel.org" <kuba@...nel.org>
CC: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        DeanKu
	<ku920601@...ltek.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: pull-request: wireless-next-2024-03-08

On Fri, 2024-03-08 at 18:50 +0200, Kalle Valo wrote:
> 
> Jakub Kicinski <kuba@...nel.org> writes:
> 
> > for a non-urgent follow up. Doesn't look like an obvious false positive.
> 
> Ping, could you fix this, please? In the patch please add Closes tag
> pointing to Jakub's email and mark it for wireless tree (assuming the
> merge window starts on Sunday, otherwise we take it to wireless-next).
> 

I have sent a fix [1], and that is a typo instead (0x55f vs 0x5ff).
Thanks for the finding.

Ping-Ke

[1] https://lore.kernel.org/linux-wireless/20240309001348.9906-1-pkshih@realtek.com/T/#u