From: Marc Zyngier <maz@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] irqchip/irq-mvebu-icu: Remove redundant error printing in mvebu_icu_probe()
Date: Tue, 11 May 2021 13:08:11 +0100 [thread overview]
Message-ID: <8244b6349a60783f8d0cb7edd12a0292@kernel.org> (raw)
In-Reply-To: <20210511120107.5781-1-thunder.leizhen@huawei.com>
Hi Zhen,
On 2021-05-11 13:01, Zhen Lei wrote:
> When devm_ioremap_resource() fails, a clear enough error message will
> be
> printed by its subfunction __devm_ioremap_resource(). The error
> information contains the device name, failure cause, and possibly
> resource
> information.
>
> Therefore, remove the error printing here to simplify code and reduce
> the
> binary size.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
I'm all grateful for these changes, but can you please organise them
in a series and send all the irqchip-related changes at once, instead
of one patch every two hours?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-11 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 12:01 [PATCH 1/1] irqchip/irq-mvebu-icu: Remove redundant error printing in mvebu_icu_probe() Zhen Lei
2021-05-11 12:08 ` Marc Zyngier [this message]
2021-05-11 12:11 ` Leizhen (ThunderTown)
2021-05-12 12:23 ` Leizhen (ThunderTown)
2021-05-12 12:25 ` Leizhen (ThunderTown)
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=8244b6349a60783f8d0cb7edd12a0292@kernel.org \
--to=maz@kernel.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@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