From: Valentine <valentine.barshak@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>, Jingoo Han <jg1.han@samsung.com>
Cc: 'Bjorn Helgaas' <bhelgaas@google.com>,
'Wei Yongjun' <weiyj.lk@gmail.com>,
'Wei Yongjun' <yongjun_wei@trendmicro.com.cn>,
linux-pci@vger.kernel.org, 'Magnus Damm' <magnus.damm@gmail.com>,
'Kuninori Morimoto' <kuninori.morimoto.gx@renesas.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar: fix return value check in rcar_pci_probe()
Date: Fri, 13 Dec 2013 16:06:54 +0400 [thread overview]
Message-ID: <52AAF85E.80206@cogentembedded.com> (raw)
In-Reply-To: <20131211023006.GN19992@verge.net.au>
On 12/11/2013 06:30 AM, Simon Horman wrote:
> On Mon, Dec 09, 2013 at 10:46:17AM +0900, Jingoo Han wrote:
>> On Sunday, December 08, 2013 7:50 AM, Bjorn Helgaas wrote:
>>> On Tue, Nov 19, 2013 at 11:40:28AM +0800, Wei Yongjun wrote:
>>>> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>>>>
>>>> In case of error, the function devm_ioremap_resource() returns ERR_PTR()
>>>> and never returns NULL. The NULL test in the return value check should
>>>> be replaced with IS_ERR().
>>>>
>>>> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>>>
>>> Applied with Jingoo's reviewed-by to pci/host-rcar for v3.14, thanks!
>>>
>>> For drivers/pci/host/*, I normally look for an ack from the responsible
>>> person, but this patch is trivial enough that I'm fine taking it without
>>> that. But for more significant changes, I don't have any notes about who
>>> should own pci-rcar-gen2.c. Valentine could be a candidate since he added
>>> it in the first place? Or Jingoo?
Sorry, I didn't ack since I thought it was not really needed for a trivial
change like this one that had already been reviewed by Jingoo.
>>
>> (+cc Simon Horman, Magnus Damm, Kuninori Morimoto, linux-sh mailing-list)
>>
>> Hi Bjorn,
>>
>> I think that Valentine could be a candidate, because he is an author.
>> However, pci-rcar-gen2.c is working on Renesas SoC, so, it may be
>> necessary to get ACK from Renesas people such as Simon Horman,
>> Magnus Damm, and Kuninori Morimoto.
>>
>> Simon Horman, Magnus Damm, and Kuninori Morimoto,
>> Who is a proper person responsible for RCar Gen PCIe driver?
>> (drivers/pci/host/pci-rcar-gen2.c)
>
> Good question.
>
> My feeling is that as it relates to Renesas ARM SoCs that
> responsibility at least in part defaults to the Renesas ARM SoC
> maintainers, Magnus and myself.
>
> So I think it would be best if the following were CCed on any patches
> to this driver:
>
> Simon Horman <horms@verge.net.au>
> Magnus Damm <magnus.damm@gmail.com>
> linux-sh@vger.kernel.org
I agree.
>
> I would not be opposed for there being a MAINTAINERS file entry to that effect.
>
> I will let Valentine volunteer himself if he wants to.
I'll try to track the e-mails related to this driver as well.
Not sure if I want myself in the MAINTAINERS though, since it would probably
mean that "try to" should be changed to "have to" in my statement above.
Thanks,
Val.
>
>>
>> Best regards,
>> Jingoo Han
>>
>>>
>>> Bjorn
>>>
>>>> ---
>>>> drivers/pci/host/pci-rcar-gen2.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/pci/host/pci-rcar-gen2.c b/drivers/pci/host/pci-rcar-gen2.c
>>>> index cbaa5c4..96d1182 100644
>>>> --- a/drivers/pci/host/pci-rcar-gen2.c
>>>> +++ b/drivers/pci/host/pci-rcar-gen2.c
>>>> @@ -276,8 +276,8 @@ static int __init rcar_pci_probe(struct platform_device *pdev)
>>>>
>>>> cfg_res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>>> reg = devm_ioremap_resource(&pdev->dev, cfg_res);
>>>> - if (!reg)
>>>> - return -ENODEV;
>>>> + if (IS_ERR(reg))
>>>> + return PTR_ERR(reg);
>>>>
>>>> mem_res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
>>>> if (!mem_res || !mem_res->start)
>>>>
>>
WARNING: multiple messages have this Message-ID (diff)
From: Valentine <valentine.barshak@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>, Jingoo Han <jg1.han@samsung.com>
Cc: 'Bjorn Helgaas' <bhelgaas@google.com>,
'Wei Yongjun' <weiyj.lk@gmail.com>,
'Wei Yongjun' <yongjun_wei@trendmicro.com.cn>,
linux-pci@vger.kernel.org, 'Magnus Damm' <magnus.damm@gmail.com>,
'Kuninori Morimoto' <kuninori.morimoto.gx@renesas.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar: fix return value check in rcar_pci_probe()
Date: Fri, 13 Dec 2013 12:06:54 +0000 [thread overview]
Message-ID: <52AAF85E.80206@cogentembedded.com> (raw)
In-Reply-To: <20131211023006.GN19992@verge.net.au>
On 12/11/2013 06:30 AM, Simon Horman wrote:
> On Mon, Dec 09, 2013 at 10:46:17AM +0900, Jingoo Han wrote:
>> On Sunday, December 08, 2013 7:50 AM, Bjorn Helgaas wrote:
>>> On Tue, Nov 19, 2013 at 11:40:28AM +0800, Wei Yongjun wrote:
>>>> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>>>>
>>>> In case of error, the function devm_ioremap_resource() returns ERR_PTR()
>>>> and never returns NULL. The NULL test in the return value check should
>>>> be replaced with IS_ERR().
>>>>
>>>> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>>>
>>> Applied with Jingoo's reviewed-by to pci/host-rcar for v3.14, thanks!
>>>
>>> For drivers/pci/host/*, I normally look for an ack from the responsible
>>> person, but this patch is trivial enough that I'm fine taking it without
>>> that. But for more significant changes, I don't have any notes about who
>>> should own pci-rcar-gen2.c. Valentine could be a candidate since he added
>>> it in the first place? Or Jingoo?
Sorry, I didn't ack since I thought it was not really needed for a trivial
change like this one that had already been reviewed by Jingoo.
>>
>> (+cc Simon Horman, Magnus Damm, Kuninori Morimoto, linux-sh mailing-list)
>>
>> Hi Bjorn,
>>
>> I think that Valentine could be a candidate, because he is an author.
>> However, pci-rcar-gen2.c is working on Renesas SoC, so, it may be
>> necessary to get ACK from Renesas people such as Simon Horman,
>> Magnus Damm, and Kuninori Morimoto.
>>
>> Simon Horman, Magnus Damm, and Kuninori Morimoto,
>> Who is a proper person responsible for RCar Gen PCIe driver?
>> (drivers/pci/host/pci-rcar-gen2.c)
>
> Good question.
>
> My feeling is that as it relates to Renesas ARM SoCs that
> responsibility at least in part defaults to the Renesas ARM SoC
> maintainers, Magnus and myself.
>
> So I think it would be best if the following were CCed on any patches
> to this driver:
>
> Simon Horman <horms@verge.net.au>
> Magnus Damm <magnus.damm@gmail.com>
> linux-sh@vger.kernel.org
I agree.
>
> I would not be opposed for there being a MAINTAINERS file entry to that effect.
>
> I will let Valentine volunteer himself if he wants to.
I'll try to track the e-mails related to this driver as well.
Not sure if I want myself in the MAINTAINERS though, since it would probably
mean that "try to" should be changed to "have to" in my statement above.
Thanks,
Val.
>
>>
>> Best regards,
>> Jingoo Han
>>
>>>
>>> Bjorn
>>>
>>>> ---
>>>> drivers/pci/host/pci-rcar-gen2.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/pci/host/pci-rcar-gen2.c b/drivers/pci/host/pci-rcar-gen2.c
>>>> index cbaa5c4..96d1182 100644
>>>> --- a/drivers/pci/host/pci-rcar-gen2.c
>>>> +++ b/drivers/pci/host/pci-rcar-gen2.c
>>>> @@ -276,8 +276,8 @@ static int __init rcar_pci_probe(struct platform_device *pdev)
>>>>
>>>> cfg_res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>>> reg = devm_ioremap_resource(&pdev->dev, cfg_res);
>>>> - if (!reg)
>>>> - return -ENODEV;
>>>> + if (IS_ERR(reg))
>>>> + return PTR_ERR(reg);
>>>>
>>>> mem_res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
>>>> if (!mem_res || !mem_res->start)
>>>>
>>
next prev parent reply other threads:[~2013-12-13 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 3:40 [PATCH] PCI: rcar: fix return value check in rcar_pci_probe() Wei Yongjun
2013-11-19 7:05 ` Jingoo Han
2013-12-07 22:50 ` Bjorn Helgaas
2013-12-09 1:46 ` Jingoo Han
2013-12-09 1:46 ` Jingoo Han
2013-12-11 2:30 ` Simon Horman
2013-12-11 2:30 ` Simon Horman
2013-12-13 12:06 ` Valentine [this message]
2013-12-13 12:06 ` Valentine
2013-12-13 17:00 ` Bjorn Helgaas
2013-12-13 17:00 ` Bjorn Helgaas
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=52AAF85E.80206@cogentembedded.com \
--to=valentine.barshak@cogentembedded.com \
--cc=bhelgaas@google.com \
--cc=horms@verge.net.au \
--cc=jg1.han@samsung.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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.