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: <20240308085839.47d8cb37@kernel.org>
Date: Fri, 8 Mar 2024 08:58:39 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Kalle Valo <kvalo@...nel.org>
Cc: netdev@...r.kernel.org, linux-wireless@...r.kernel.org, Ching-Te Ku
 <ku920601@...ltek.com>, Ping-Ke Shih <pkshih@...ltek.com>
Subject: Re: pull-request: wireless-next-2024-03-08

On Fri, 08 Mar 2024 18:50:11 +0200 Kalle Valo wrote:
> > coccicheck flags:
> >
> > drivers/net/wireless/realtek/rtw89/rtw8922a.c:2235:2-4: WARNING: possible condition with no effect (if == else)  
> 
> Thanks, but how did you find this? I'm asking just to understand your process, at
> least the pull request shows all green:
> 
> https://patchwork.kernel.org/project/netdevbpf/patch/20240308100429.B8EA2C433F1@smtp.kernel.org/
> 
> We don't run coccicheck so it's not surprising there are new warnings.

We have another bunch of tests now which run on all outstanding patches
every 3 hours. selftests for example. We need to aggregate because
there's too much code getting posted. One of the "tests" we run is
make coccicheck.

https://github.com/kuba-moo/nipa/blob/master/contest/tests/cocci-check.sh

it's supposed to report back to patchwork as "contest", but
the reporting is not 100% accurate I need to fix it :| 
I look here instead: https://netdev.bots.linux.dev/status.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ