Message ID | 20240308100429.B8EA2C433F1@smtp.kernel.org (mailing list archive) |
---|---|
State | Not Applicable |
Delegated to: | Kalle Valo |
Headers | show |
Series | pull-request: wireless-next-2024-03-08 | expand |
On Fri, 8 Mar 2024 10:04:29 +0000 (UTC) Kalle Valo wrote: > here's a pull request to net-next tree, more info below. Please let me know if > there are any problems. coccicheck flags: drivers/net/wireless/realtek/rtw89/rtw8922a.c:2235:2-4: WARNING: possible condition with no effect (if == else) for a non-urgent follow up. Doesn't look like an obvious false positive.
Jakub Kicinski <kuba@kernel.org> writes: > On Fri, 8 Mar 2024 10:04:29 +0000 (UTC) Kalle Valo wrote: >> here's a pull request to net-next tree, more info below. Please let me know if >> there are any problems. > > 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. > 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).
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
Hello: This pull request was applied to netdev/net-next.git (main) by Jakub Kicinski <kuba@kernel.org>: On Fri, 8 Mar 2024 10:04:29 +0000 (UTC) you wrote: > Hi, > > here's a pull request to net-next tree, more info below. Please let me know if > there are any problems. > > Kalle > > [...] Here is the summary with links: - pull-request: wireless-next-2024-03-08 https://git.kernel.org/netdev/net-next/c/75c2946db360 You are awesome, thank you!
On Fri, 2024-03-08 at 18:50 +0200, Kalle Valo wrote: > > Jakub Kicinski <kuba@kernel.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