From: majun258@huawei.com (majun (F))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] Add the driver of mbigen interrupt controller
Date: Mon, 7 Sep 2015 09:17:01 +0800 [thread overview]
Message-ID: <55ECE58D.6050602@huawei.com> (raw)
In-Reply-To: <CALW4P+KQEJsKCbnXeyup2Z2vNGY9jXKZKafQ+hSvc5_U5O+vtQ@mail.gmail.com>
Hi Alexey:
? 2015/9/4 8:56, Alexey Klimov ??:
> Hi Ma Jun,
>
> On Tue, Sep 1, 2015 at 4:45 AM, majun (F) <majun258@huawei.com> wrote:
>> Hi Alexey:
>>
[...]
>>>> + mgn_chip->base = base;
>>>> + mgn_chip->node = node;
>>>> +
>>>> + domain = irq_domain_add_tree(node, &mbigen_domain_ops, mgn_chip);
>>>> + mgn_chip->domain = domain;
>>>> +
>>>> + raw_spin_lock_init(&mgn_chip->lock);
>>>> + INIT_LIST_HEAD(&mgn_chip->entry);
>>>> + INIT_LIST_HEAD(&mgn_chip->mbigen_device_list);
>>>> +
>>>> + for_each_child_of_node(node, child) {
>>>> + mbigen_device_init(mgn_chip, child);
>>>
>>> You don't check error from mbigen_device_init()
>> I don't think we need to check errors here.
>> mbigen_device_init() handle all errors.
>
> For my eyes, mbigen_device_init() is static and used only once here.
> Here you don't check return value from it. If this is correct you can
> convert mbigen_device_init() to return void unless you have future
> plans to modify it.
>
> Or you have option to check return value here and add error path.
Ok, This will be changed in next version.
>
> Please add me to cc to next version of patch set which I guess will be v5.
>
Got it. I will add you to cc list in next version.
Thanks for you review !
Ma Jun
WARNING: multiple messages have this Message-ID (diff)
From: "majun (F)" <majun258@huawei.com>
To: Alexey Klimov <klimov.linux@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <Will.Deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>, <marc.zyngier@arm.com>,
<jason@lakedaemon.net>, Thomas Gleixner <tglx@linutronix.de>,
<lizefan@huawei.com>, <huxinwei@huawei.com>,
<dingtianhong@huawei.com>, <zhaojunhua@hisilicon.com>,
Kenneth Lee <liguozhu@hisilicon.com>, <xuwei5@hisilicon.com>,
<wei.chenwei@hisilicon.com>, <guohanjun@huawei.com>,
<wuyun.wu@huawei.com>, Guodong Xu <guodong.xu@linaro.org>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
"Usman Ahmad" <usman.ahmad@linaro.org>
Subject: Re: [PATCH v4 1/2] Add the driver of mbigen interrupt controller
Date: Mon, 7 Sep 2015 09:17:01 +0800 [thread overview]
Message-ID: <55ECE58D.6050602@huawei.com> (raw)
In-Reply-To: <CALW4P+KQEJsKCbnXeyup2Z2vNGY9jXKZKafQ+hSvc5_U5O+vtQ@mail.gmail.com>
Hi Alexey:
在 2015/9/4 8:56, Alexey Klimov 写道:
> Hi Ma Jun,
>
> On Tue, Sep 1, 2015 at 4:45 AM, majun (F) <majun258@huawei.com> wrote:
>> Hi Alexey:
>>
[...]
>>>> + mgn_chip->base = base;
>>>> + mgn_chip->node = node;
>>>> +
>>>> + domain = irq_domain_add_tree(node, &mbigen_domain_ops, mgn_chip);
>>>> + mgn_chip->domain = domain;
>>>> +
>>>> + raw_spin_lock_init(&mgn_chip->lock);
>>>> + INIT_LIST_HEAD(&mgn_chip->entry);
>>>> + INIT_LIST_HEAD(&mgn_chip->mbigen_device_list);
>>>> +
>>>> + for_each_child_of_node(node, child) {
>>>> + mbigen_device_init(mgn_chip, child);
>>>
>>> You don't check error from mbigen_device_init()
>> I don't think we need to check errors here.
>> mbigen_device_init() handle all errors.
>
> For my eyes, mbigen_device_init() is static and used only once here.
> Here you don't check return value from it. If this is correct you can
> convert mbigen_device_init() to return void unless you have future
> plans to modify it.
>
> Or you have option to check return value here and add error path.
Ok, This will be changed in next version.
>
> Please add me to cc to next version of patch set which I guess will be v5.
>
Got it. I will add you to cc list in next version.
Thanks for you review !
Ma Jun
next prev parent reply other threads:[~2015-09-07 1:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 3:13 [PATCH v4 1/2] Add the driver of mbigen interrupt controller Alexey Klimov
2015-09-01 1:45 ` majun (F)
2015-09-01 1:45 ` majun (F)
2015-09-04 0:56 ` Alexey Klimov
2015-09-04 0:56 ` Alexey Klimov
2015-09-07 1:17 ` majun (F) [this message]
2015-09-07 1:17 ` majun (F)
-- strict thread matches above, loose matches on Subject: below --
2015-08-19 2:55 [PATCH v4 0/2] Support Mbigen " MaJun
2015-08-19 2:55 ` [PATCH v4 1/2] Add the driver of mbigen " MaJun
2015-08-19 2:55 ` MaJun
2015-09-21 21:53 ` Marc Zyngier
2015-09-21 21:53 ` Marc Zyngier
2015-09-23 7:24 ` majun (F)
2015-09-23 7:24 ` majun (F)
2015-09-24 19:30 ` Marc Zyngier
2015-09-24 19:30 ` Marc Zyngier
2015-09-25 11:56 ` majun (F)
2015-09-25 11:56 ` majun (F)
2015-09-28 15:46 ` Marc Zyngier
2015-09-28 15:46 ` Marc Zyngier
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=55ECE58D.6050602@huawei.com \
--to=majun258@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.