From: Tianxianting <tian.xianting@h3c.com>
To: Markus Elfring <Markus.Elfring@web.de>,
"uclinux-h8-devel@lists.sourceforge.jp"
<uclinux-h8-devel@lists.sourceforge.jp>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: RE: [PATCH] clocksource: Return negative error code in h8300_8timer_init()
Date: Wed, 2 Sep 2020 08:34:50 +0000 [thread overview]
Message-ID: <bf571d3088a4419dac147729e4206574@h3c.com> (raw)
In-Reply-To: <7356d489-2320-2a75-0999-0b3f0f8ac373@web.de>
Hi Markus,
Thanks for your comments.
No real fix, as normally , we should return a negative code,
In function h8300_8timer_init(), it set ' ret = -EINVAL ', ' ret = ENXIO' , it should be align with a negative code
static int __init h8300_8timer_init(struct device_node *node)
{
ret = ENXIO; <<<
base = of_iomap(node, 0);
if (!base) {
pr_err("failed to map registers for clockevent\n");
goto free_clk;
}
ret = -EINVAL; <<<
irq = irq_of_parse_and_map(node, 0);
if (!irq) {
pr_err("failed to get irq for clockevent\n");
goto unmap_reg;
}
-----Original Message-----
From: Markus Elfring [mailto:Markus.Elfring@web.de]
Sent: Tuesday, September 01, 2020 10:46 PM
To: tianxianting (RD) <tian.xianting@h3c.com>; uclinux-h8-devel@lists.sourceforge.jp
Cc: linux-kernel@vger.kernel.org; kernel-janitors@vger.kernel.org; Daniel Lezcano <daniel.lezcano@linaro.org>; Thomas Gleixner <tglx@linutronix.de>; Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] clocksource: Return negative error code in h8300_8timer_init()
> A negative error code should be returned
* Can an other imperative wording become helpful for the change description?
* Would you like to add the tag “Fixes” to the commit message?
Regards,
Markus
parent reply other threads:[~2020-09-02 10:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <7356d489-2320-2a75-0999-0b3f0f8ac373@web.de>]
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=bf571d3088a4419dac147729e4206574@h3c.com \
--to=tian.xianting@h3c.com \
--cc=Markus.Elfring@web.de \
--cc=daniel.lezcano@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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®