From: Moritz Fischer <mdf@kernel.org>
To: trix@redhat.com
Cc: mdf@kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] fpga: Fix dead store in fpga-bridge.c
Date: Thu, 18 Jun 2020 18:39:33 -0700 [thread overview]
Message-ID: <20200619013933.GE3685@epycbox.lan> (raw)
In-Reply-To: <20200608125446.23311-3-trix@redhat.com>
On Mon, Jun 08, 2020 at 05:54:46AM -0700, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> Using clang's scan-build/view this issue was flagged
> a dead store issue in fpga-bridge.c
>
> warning: Value stored to 'ret' is never read [deadcode.DeadStores]
> ret = id;
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/fpga/fpga-bridge.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/fpga/fpga-bridge.c b/drivers/fpga/fpga-bridge.c
> index 4bab9028940a..2deccacc3aa7 100644
> --- a/drivers/fpga/fpga-bridge.c
> +++ b/drivers/fpga/fpga-bridge.c
> @@ -328,7 +328,7 @@ struct fpga_bridge *fpga_bridge_create(struct device *dev, const char *name,
> void *priv)
> {
> struct fpga_bridge *bridge;
> - int id, ret = 0;
> + int id, ret;
>
> if (!name || !strlen(name)) {
> dev_err(dev, "Attempt to register with no name!\n");
> @@ -340,10 +340,8 @@ struct fpga_bridge *fpga_bridge_create(struct device *dev, const char *name,
> return NULL;
>
> id = ida_simple_get(&fpga_bridge_ida, 0, 0, GFP_KERNEL);
> - if (id < 0) {
> - ret = id;
> + if (id < 0)
> goto error_kfree;
> - }
>
> mutex_init(&bridge->mutex);
> INIT_LIST_HEAD(&bridge->node);
> --
> 2.18.2
>
Applied to for-next,
Thanks!
prev parent reply other threads:[~2020-06-19 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 12:54 [PATCH v2 0/2] fpga: Fix dead store trix
2020-06-08 12:54 ` [PATCH v2 1/2] fpga: Fix dead store fpga-mgr.c trix
2020-06-19 1:39 ` Moritz Fischer
2020-06-08 12:54 ` [PATCH v2 2/2] fpga: Fix dead store in fpga-bridge.c trix
2020-06-19 1:39 ` Moritz Fischer [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=20200619013933.GE3685@epycbox.lan \
--to=mdf@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trix@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: 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