From: Tushar Behera <tushar.behera@linaro.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
patches@linaro.org, linux-pci@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 13/15] pci: mvebu: Convert to use devm_ioremap_resource
Date: Tue, 11 Jun 2013 10:21:54 +0530 [thread overview]
Message-ID: <51B6ACEA.2040408@linaro.org> (raw)
In-Reply-To: <CAK9yfHzcw071CfssSdFjmN1qXOp732NOaud2G0Dcd_8KZBFbgQ@mail.gmail.com>
On 06/10/2013 07:59 PM, Sachin Kamat wrote:
> On 10 June 2013 17:05, Tushar Behera <tushar.behera@linaro.org> wrote:
>> Commit 75096579c3ac ("lib: devres: Introduce devm_ioremap_resource()")
>> introduced devm_ioremap_resource() and deprecated the use of
>> devm_request_and_ioremap().
>>
>> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
>> CC: linux-pci@vger.kernel.org
>> CC: Bjorn Helgaas <bhelgaas@google.com>
>> ---
>> drivers/pci/host/pci-mvebu.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/pci/host/pci-mvebu.c b/drivers/pci/host/pci-mvebu.c
>> index 13a633b..e714876 100644
>> --- a/drivers/pci/host/pci-mvebu.c
>> +++ b/drivers/pci/host/pci-mvebu.c
>> @@ -752,7 +752,7 @@ mvebu_pcie_map_registers(struct platform_device *pdev,
>> if (ret)
>> return NULL;
>>
>> - return devm_request_and_ioremap(&pdev->dev, ®s);
>> + return devm_ioremap_resource(&pdev->dev, ®s);
>> }
>>
>> static int __init mvebu_pcie_probe(struct platform_device *pdev)
>> @@ -842,9 +842,10 @@ static int __init mvebu_pcie_probe(struct platform_device *pdev)
>> continue;
>>
>> port->base = mvebu_pcie_map_registers(pdev, child, port);
>> - if (!port->base) {
>> + if (IS_ERR(port->base)) {
>> dev_err(&pdev->dev, "PCIe%d.%d: cannot map registers\n",
>> port->port, port->lane);
>
> This error message is redundant.
>
It provides a little more information regarding the port and lane number
which might be useful in debugging.
>> + port->base = NULL;
> Probably this is also not needed.
>
I was not sure about the default error value for port->base, hence I
replicated the old behaviour.
Thanks.
--
Tushar Behera
next prev parent reply other threads:[~2013-06-11 4:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 11:34 [PATCH 00/15] Convert to use devm_ioremap_resource Tushar Behera
2013-06-10 11:35 ` [PATCH 13/15] pci: mvebu: " Tushar Behera
2013-06-10 14:29 ` Sachin Kamat
2013-06-11 4:51 ` Tushar Behera [this message]
2013-06-17 9:16 ` [PATCH V2 6/6] " Tushar Behera
2013-07-23 18:38 ` Bjorn Helgaas
2013-07-23 20:19 ` Ezequiel Garcia
2013-08-06 10:39 ` Thomas Petazzoni
2013-08-06 18:10 ` 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=51B6ACEA.2040408@linaro.org \
--to=tushar.behera@linaro.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sachin.kamat@linaro.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).