From: Michael Ellerman <mpe@ellerman.id.au>
To: Gautam Menghani <gautam@linux.ibm.com>,
npiggin@gmail.com, christophe.leroy@csgroup.eu
Cc: Gautam Menghani <gautam@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/powerpc: Remove unnecessary endian conversion code in XICS
Date: Mon, 03 Jul 2023 16:41:41 +1000 [thread overview]
Message-ID: <878rbxwl7e.fsf@mail.lhotse> (raw)
In-Reply-To: <20230630055628.17790-1-gautam@linux.ibm.com>
Gautam Menghani <gautam@linux.ibm.com> writes:
> Remove an unnecessary piece of code that does an endianness conversion but
> does not use the result. The following warning was reported by Clang's
> static analyzer:
>
> arch/powerpc/sysdev/xics/ics-opal.c:114:2: warning: Value stored to
> 'server' is never read [deadcode.DeadStores]
> server = be16_to_cpu(oserver);
>
> As the result of endianness conversion is never used, delete the line
> and fix the warning.
>
> Signed-off-by: Gautam Menghani <gautam@linux.ibm.com>
> ---
> arch/powerpc/sysdev/xics/ics-opal.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/powerpc/sysdev/xics/ics-opal.c b/arch/powerpc/sysdev/xics/ics-opal.c
> index 6cfbb4fac7fb..5fe73dabab79 100644
> --- a/arch/powerpc/sysdev/xics/ics-opal.c
> +++ b/arch/powerpc/sysdev/xics/ics-opal.c
> @@ -111,7 +111,6 @@ static int ics_opal_set_affinity(struct irq_data *d,
> __func__, d->irq, hw_irq, rc);
> return -1;
> }
> - server = be16_to_cpu(oserver);
>
> wanted_server = xics_get_irq_server(d->irq, cpumask, 1);
> if (wanted_server < 0) {
My first question with a patch like this is always going to be "how did
the code end up like this?"
Has the code changed and this assignment became unused? If so the commit
that did that should be identified.
If the code has always been like this that's also useful to know. Or
something else happened for it to end up this way :)
The second question will be "is there actually a bug here?". ie. should
server actually be used, and the bug is not that it's a dead assignment
but rather that server is not where it should be.
cheers
next prev parent reply other threads:[~2023-07-03 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 5:56 [PATCH] arch/powerpc: Remove unnecessary endian conversion code in XICS Gautam Menghani
2023-07-03 6:41 ` Michael Ellerman [this message]
2023-07-06 7:50 ` Jordan Niethe
2023-07-11 9:33 ` Gautam Menghani
2023-07-26 8:07 ` Gautam Menghani
2023-07-26 9:12 ` Gautam Menghani
2023-07-29 10:54 ` Michael Ellerman
2023-07-31 12:00 ` Gautam Menghani
-- strict thread matches above, loose matches on Subject: below --
2023-06-30 6:13 Gautam Menghani
2023-06-30 6:16 ` Gautam Menghani
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=878rbxwl7e.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=gautam@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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