From: patchwork-bot+netdevbpf@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
jerinj@marvell.com, hkelam@marvell.com, sbhatta@marvell.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] octeontx2-af: Remove redundant initialization of variable blkaddr
Date: Fri, 17 Sep 2021 13:10:07 +0000 [thread overview]
Message-ID: <163188420747.25822.3507781673338733348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210917120333.48074-1-colin.king@canonical.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 17 Sep 2021 13:03:33 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The variable blkaddr is being initialized with a value that is never
> read, it is being updated later on in a for-loop. The assignment is
> redundant and can be removed.
>
> Addresses-Coverity: ("Unused value")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>
> [...]
Here is the summary with links:
- [next] octeontx2-af: Remove redundant initialization of variable blkaddr
https://git.kernel.org/netdev/net-next/c/3503e673db23
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:[~2021-09-17 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 12:03 [PATCH][next] octeontx2-af: Remove redundant initialization of variable blkaddr Colin King
2021-09-17 13:10 ` 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=163188420747.25822.3507781673338733348.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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: link
Be 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.