From: Haowen Bai <baihaowen@meizu.com> To: <kvalo@kernel.org>, <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com> Cc: <linux-wireless@vger.kernel.org>, <b43-dev@lists.infradead.org>, <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Haowen Bai <baihaowen@meizu.com> Subject: [PATCH V3] b43legacy: Fix assigning negative value to unsigned variable Date: Fri, 25 Mar 2022 18:17:13 +0800 [thread overview] Message-ID: <1648203433-8736-1-git-send-email-baihaowen@meizu.com> (raw) fix warning reported by smatch: drivers/net/wireless/broadcom/b43legacy/phy.c:1181 b43legacy_phy_lo_b_measure() warn: assigning (-772) to unsigned variable 'fval' Signed-off-by: Haowen Bai <baihaowen@meizu.com> --- V1->V2: modify title of this patch V2->V3: modify prefix of title b43legacy drivers/net/wireless/broadcom/b43legacy/phy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/broadcom/b43legacy/phy.c b/drivers/net/wireless/broadcom/b43legacy/phy.c index 05404fb..c1395e6 100644 --- a/drivers/net/wireless/broadcom/b43legacy/phy.c +++ b/drivers/net/wireless/broadcom/b43legacy/phy.c @@ -1123,7 +1123,7 @@ void b43legacy_phy_lo_b_measure(struct b43legacy_wldev *dev) struct b43legacy_phy *phy = &dev->phy; u16 regstack[12] = { 0 }; u16 mls; - u16 fval; + s16 fval; int i; int j; -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Haowen Bai <baihaowen@meizu.com> To: <kvalo@kernel.org>, <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com> Cc: <linux-wireless@vger.kernel.org>, <b43-dev@lists.infradead.org>, <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Haowen Bai <baihaowen@meizu.com> Subject: [PATCH V3] b43legacy: Fix assigning negative value to unsigned variable Date: Fri, 25 Mar 2022 18:17:13 +0800 [thread overview] Message-ID: <1648203433-8736-1-git-send-email-baihaowen@meizu.com> (raw) fix warning reported by smatch: drivers/net/wireless/broadcom/b43legacy/phy.c:1181 b43legacy_phy_lo_b_measure() warn: assigning (-772) to unsigned variable 'fval' Signed-off-by: Haowen Bai <baihaowen@meizu.com> --- V1->V2: modify title of this patch V2->V3: modify prefix of title b43legacy drivers/net/wireless/broadcom/b43legacy/phy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/broadcom/b43legacy/phy.c b/drivers/net/wireless/broadcom/b43legacy/phy.c index 05404fb..c1395e6 100644 --- a/drivers/net/wireless/broadcom/b43legacy/phy.c +++ b/drivers/net/wireless/broadcom/b43legacy/phy.c @@ -1123,7 +1123,7 @@ void b43legacy_phy_lo_b_measure(struct b43legacy_wldev *dev) struct b43legacy_phy *phy = &dev->phy; u16 regstack[12] = { 0 }; u16 mls; - u16 fval; + s16 fval; int i; int j; -- 2.7.4 _______________________________________________ b43-dev mailing list b43-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/b43-dev
next reply other threads:[~2022-03-25 10:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-25 10:17 Haowen Bai [this message] 2022-03-25 10:17 ` [PATCH V3] b43legacy: Fix assigning negative value to unsigned variable Haowen Bai 2022-04-06 12:13 ` Kalle Valo 2022-04-06 12:13 ` Kalle Valo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1648203433-8736-1-git-send-email-baihaowen@meizu.com \ --to=baihaowen@meizu.com \ --cc=b43-dev@lists.infradead.org \ --cc=davem@davemloft.net \ --cc=kuba@kernel.org \ --cc=kvalo@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-wireless@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=pabeni@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.