mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Bo Yan <byan@nvidia.com>
Cc: <tglx@linutronix.de>, <jason@lakedaemon.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irqchip/gic: check return value of of_address_to_resource
Date: Sat, 7 Jul 2018 11:01:47 +0100	[thread overview]
Message-ID: <20180707110147.64905726@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <c892593d-8824-e6c5-b435-0902fd0e7fde@nvidia.com>

On Thu, 5 Jul 2018 12:32:22 -0700
Bo Yan <byan@nvidia.com> wrote:

> Marc,
> 
> Sorry for the previous reply. My email settings were not correct, so it inserted those confidentiality text, which was not what I intended.
> 
> This is what I think:
> 
> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> index ced10c4..0b60bb0 100644
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> @@ -1284,7 +1284,7 @@ static bool gic_check_eoimode(struct device_node *node, void __iomem **base)
>   {
>          struct resource cpuif_res;
> 
> -       of_address_to_resource(node, 1, &cpuif_res);
> +       (void)of_address_to_resource(node, 1, &cpuif_res);
> 
>          if (!is_hyp_mode_available())
>                  return false;
> 
> We are 100% sure of_address_to_resource will succeed in this particular case, so "(void)" will help suppress Coverity warning.

In all honesty. I don't see the point of patching the kernel to silence
a warning when we know that this is a false positive. I'm sure you can
flag that one as "false positive" in Coverity.

Thanks,

	M.
-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2018-07-07 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 18:20 Bo Yan
2018-07-05 19:13 ` Marc Zyngier
2018-07-05 19:18   ` Bo Yan
2018-07-05 19:32     ` Bo Yan
2018-07-07 10:01       ` Marc Zyngier [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=20180707110147.64905726@why.wild-wind.fr.eu.org \
    --to=marc.zyngier@arm.com \
    --cc=byan@nvidia.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®