From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
mailhol.vincent@wanadoo.fr, nathan@kernel.org
Subject: Re: [PATCH net-next] can: pch_can: pch_can_error(): initialize errc before using it
Date: Fri, 22 Jul 2022 02:00:13 +0000 [thread overview]
Message-ID: <165845521387.922.8823304957699439976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220721163042.3448384-2-mkl@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (master)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Thu, 21 Jul 2022 18:30:42 +0200 you wrote:
> From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
>
> After commit 3a5c7e4611dd, the variable errc is accessed before being
> initialized, c.f. below W=2 warning:
>
> | In function 'pch_can_error',
> | inlined from 'pch_can_poll' at drivers/net/can/pch_can.c:739:4:
> | drivers/net/can/pch_can.c:501:29: warning: 'errc' may be used uninitialized [-Wmaybe-uninitialized]
> | 501 | cf->data[6] = errc & PCH_TEC;
> | | ^
> | drivers/net/can/pch_can.c: In function 'pch_can_poll':
> | drivers/net/can/pch_can.c:484:13: note: 'errc' was declared here
> | 484 | u32 errc, lec;
> | | ^~~~
>
> [...]
Here is the summary with links:
- [net-next] can: pch_can: pch_can_error(): initialize errc before using it
https://git.kernel.org/netdev/net-next/c/9950f1121133
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-07-22 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 16:30 [PATCH net-next 0/1] pull-request: can-next 2022-07-21 Marc Kleine-Budde
2022-07-21 16:30 ` [PATCH net-next] can: pch_can: pch_can_error(): initialize errc before using it Marc Kleine-Budde
2022-07-22 2:00 ` patchwork-bot+netdevbpf [this message]
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=165845521387.922.8823304957699439976.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox