From: Marc Zyngier <maz@kernel.org>
To: <Claudiu.Beznea@microchip.com>
Cc: <yangyingliang@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH -next] irqchip/mchp-eic: Fix return value check in mchp_eic_init()
Date: Mon, 25 Oct 2021 11:30:46 +0100 [thread overview]
Message-ID: <87ee89bdm1.wl-maz@kernel.org> (raw)
In-Reply-To: <704dd2cf-e181-371f-719a-254051fd5895@microchip.com>
On Mon, 25 Oct 2021 10:40:15 +0100,
<Claudiu.Beznea@microchip.com> wrote:
>
> On 25.10.2021 10:44, Claudiu Beznea - M18063 wrote:
> > On 25.10.2021 08:00, Yang Yingliang wrote:
> >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >>
> >> In case of error, the function of_iomap() returns NULL pointer
> >> not ERR_PTR(). The IS_ERR() test in the return value check
> >> should be replaced with NULL test.
> >>
> >> Reported-by: Hulk Robot <hulkci@huawei.com>
> >> Signed-off-by: Yang Yingliang <yangyingliang@huawei.
> > Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>
> Forgot to mention, can you add the Fixes tag?
There is no real need for one when the offending patch is in the same
merge window, and will be in the same pull request.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-10-25 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 5:00 [PATCH -next] irqchip/mchp-eic: Fix return value check in mchp_eic_init() Yang Yingliang
2021-10-25 7:44 ` Claudiu.Beznea
2021-10-25 9:40 ` Claudiu.Beznea
2021-10-25 10:30 ` Marc Zyngier [this message]
2021-10-25 8:11 ` [irqchip: irq/irqchip-next] " irqchip-bot for Yang Yingliang
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=87ee89bdm1.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@huawei.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