From: Stephen Warren <swarren@wwwdotorg.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
kernel-janitors@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] PCI: tegra: replace devm_request_and_ioremap by devm_ioremap_resource
Date: Mon, 19 Aug 2013 20:56:45 +0000 [thread overview]
Message-ID: <5212868D.2050604@wwwdotorg.org> (raw)
In-Reply-To: <20130819193339.GB4961@mithrandir>
On 08/19/2013 01:33 PM, Thierry Reding wrote:
> On Mon, Aug 19, 2013 at 02:15:39PM +0200, Julia Lawall wrote:
>>
>>
>> On Mon, 19 Aug 2013, Thierry Reding wrote:
>>
>>> On Mon, Aug 19, 2013 at 02:07:54PM +0200, Julia Lawall wrote:
>>>>
>>>>
>>>> On Mon, 19 Aug 2013, Thierry Reding wrote:
>>>>
>>>>> On Mon, Aug 19, 2013 at 01:20:35PM +0200, Julia Lawall
>>>>> wrote:
>>>>>> From: Julia Lawall <Julia.Lawall@lip6.fr>
>>>>>>
>>>>>> Use devm_ioremap_resource instead of
>>>>>> devm_request_and_ioremap.
>>>>>>
>>>>>> This was done using the semantic patch
>>>>>> scripts/coccinelle/api/devm_ioremap_resource.cocci
>>>>>>
>>>>>> Error-handling code was manually removed from the
>>>>>> associated calls to platform_get_resource.
>>>>>>
>>>>>> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>>>>>>
>>>>>> --- The first block of modified code is followed by a
>>>>>> call to devm_request_mem_region for pcie->cs with no
>>>>>> associated ioremap. Should ioremap be used in this case
>>>>>> as well?
>>>>>
>>>>> No. The pcie->cs resource is 256 MiB so it's challenging to
>>>>> map it at once. Furthermore it requires a non-linear
>>>>> mapping so we do it on demand.
>>>>
>>>> OK, thanks for the explanation. Is the comment, though, a
>>>> little misleading, since the mapping is not done here?
>>>>
>>>> /* request and remap configuration space */
>>>
>>> Yes, that's misleading. Given that it doesn't really add
>>> anything useful information either, perhaps I should just
>>> remove it.
>>
>> OK, or maybe something like
>>
>> /* request configuration space, but remap later, on demand */
>>
>> To make it clear that something different is intended than the
>> devm_ioremap_resources that come just before..
>
> Yes, that works for me too. Can you respin the patch with the
> comment updated and my Acked-by and Tested-by so Bjorn can pick it
> up?
Just a note though: Since the Tegra PCIe driver is only being added in
v3.12-rc1, and that add is happening in the Tegra/arm-soc tree, Bjorn
won't be able to accept the patch until after v3.12-rc1. Perhaps the
arm-soc tree could take the patch before then though...
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
kernel-janitors@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] PCI: tegra: replace devm_request_and_ioremap by devm_ioremap_resource
Date: Mon, 19 Aug 2013 14:56:45 -0600 [thread overview]
Message-ID: <5212868D.2050604@wwwdotorg.org> (raw)
In-Reply-To: <20130819193339.GB4961@mithrandir>
On 08/19/2013 01:33 PM, Thierry Reding wrote:
> On Mon, Aug 19, 2013 at 02:15:39PM +0200, Julia Lawall wrote:
>>
>>
>> On Mon, 19 Aug 2013, Thierry Reding wrote:
>>
>>> On Mon, Aug 19, 2013 at 02:07:54PM +0200, Julia Lawall wrote:
>>>>
>>>>
>>>> On Mon, 19 Aug 2013, Thierry Reding wrote:
>>>>
>>>>> On Mon, Aug 19, 2013 at 01:20:35PM +0200, Julia Lawall
>>>>> wrote:
>>>>>> From: Julia Lawall <Julia.Lawall@lip6.fr>
>>>>>>
>>>>>> Use devm_ioremap_resource instead of
>>>>>> devm_request_and_ioremap.
>>>>>>
>>>>>> This was done using the semantic patch
>>>>>> scripts/coccinelle/api/devm_ioremap_resource.cocci
>>>>>>
>>>>>> Error-handling code was manually removed from the
>>>>>> associated calls to platform_get_resource.
>>>>>>
>>>>>> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>>>>>>
>>>>>> --- The first block of modified code is followed by a
>>>>>> call to devm_request_mem_region for pcie->cs with no
>>>>>> associated ioremap. Should ioremap be used in this case
>>>>>> as well?
>>>>>
>>>>> No. The pcie->cs resource is 256 MiB so it's challenging to
>>>>> map it at once. Furthermore it requires a non-linear
>>>>> mapping so we do it on demand.
>>>>
>>>> OK, thanks for the explanation. Is the comment, though, a
>>>> little misleading, since the mapping is not done here?
>>>>
>>>> /* request and remap configuration space */
>>>
>>> Yes, that's misleading. Given that it doesn't really add
>>> anything useful information either, perhaps I should just
>>> remove it.
>>
>> OK, or maybe something like
>>
>> /* request configuration space, but remap later, on demand */
>>
>> To make it clear that something different is intended than the
>> devm_ioremap_resources that come just before..
>
> Yes, that works for me too. Can you respin the patch with the
> comment updated and my Acked-by and Tested-by so Bjorn can pick it
> up?
Just a note though: Since the Tegra PCIe driver is only being added in
v3.12-rc1, and that add is happening in the Tegra/arm-soc tree, Bjorn
won't be able to accept the patch until after v3.12-rc1. Perhaps the
arm-soc tree could take the patch before then though...
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Julia Lawall <julia.lawall-L2FTfq7BK8M@public.gmane.org>,
kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/7] PCI: tegra: replace devm_request_and_ioremap by devm_ioremap_resource
Date: Mon, 19 Aug 2013 14:56:45 -0600 [thread overview]
Message-ID: <5212868D.2050604@wwwdotorg.org> (raw)
In-Reply-To: <20130819193339.GB4961@mithrandir>
On 08/19/2013 01:33 PM, Thierry Reding wrote:
> On Mon, Aug 19, 2013 at 02:15:39PM +0200, Julia Lawall wrote:
>>
>>
>> On Mon, 19 Aug 2013, Thierry Reding wrote:
>>
>>> On Mon, Aug 19, 2013 at 02:07:54PM +0200, Julia Lawall wrote:
>>>>
>>>>
>>>> On Mon, 19 Aug 2013, Thierry Reding wrote:
>>>>
>>>>> On Mon, Aug 19, 2013 at 01:20:35PM +0200, Julia Lawall
>>>>> wrote:
>>>>>> From: Julia Lawall <Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
>>>>>>
>>>>>> Use devm_ioremap_resource instead of
>>>>>> devm_request_and_ioremap.
>>>>>>
>>>>>> This was done using the semantic patch
>>>>>> scripts/coccinelle/api/devm_ioremap_resource.cocci
>>>>>>
>>>>>> Error-handling code was manually removed from the
>>>>>> associated calls to platform_get_resource.
>>>>>>
>>>>>> Signed-off-by: Julia Lawall <Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
>>>>>>
>>>>>> --- The first block of modified code is followed by a
>>>>>> call to devm_request_mem_region for pcie->cs with no
>>>>>> associated ioremap. Should ioremap be used in this case
>>>>>> as well?
>>>>>
>>>>> No. The pcie->cs resource is 256 MiB so it's challenging to
>>>>> map it at once. Furthermore it requires a non-linear
>>>>> mapping so we do it on demand.
>>>>
>>>> OK, thanks for the explanation. Is the comment, though, a
>>>> little misleading, since the mapping is not done here?
>>>>
>>>> /* request and remap configuration space */
>>>
>>> Yes, that's misleading. Given that it doesn't really add
>>> anything useful information either, perhaps I should just
>>> remove it.
>>
>> OK, or maybe something like
>>
>> /* request configuration space, but remap later, on demand */
>>
>> To make it clear that something different is intended than the
>> devm_ioremap_resources that come just before..
>
> Yes, that works for me too. Can you respin the patch with the
> comment updated and my Acked-by and Tested-by so Bjorn can pick it
> up?
Just a note though: Since the Tegra PCIe driver is only being added in
v3.12-rc1, and that add is happening in the Tegra/arm-soc tree, Bjorn
won't be able to accept the patch until after v3.12-rc1. Perhaps the
arm-soc tree could take the patch before then though...
next prev parent reply other threads:[~2013-08-19 20:56 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 11:20 [PATCH 0/7] replace devm_request_and_ioremap by devm_ioremap_resource Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-19 11:20 ` [PATCH 1/7] PCI: tegra: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-19 12:02 ` Thierry Reding
2013-08-19 12:02 ` Thierry Reding
2013-08-19 12:07 ` Julia Lawall
2013-08-19 12:07 ` Julia Lawall
2013-08-19 12:07 ` Julia Lawall
2013-08-19 12:12 ` Thierry Reding
2013-08-19 12:12 ` Thierry Reding
2013-08-19 12:15 ` Julia Lawall
2013-08-19 12:15 ` Julia Lawall
2013-08-19 12:15 ` Julia Lawall
2013-08-19 19:33 ` Thierry Reding
2013-08-19 19:33 ` Thierry Reding
2013-08-19 19:33 ` Thierry Reding
2013-08-19 20:56 ` Stephen Warren [this message]
2013-08-19 20:56 ` Stephen Warren
2013-08-19 20:56 ` Stephen Warren
2013-08-20 9:13 ` Julia Lawall
2013-08-20 9:13 ` Julia Lawall
2013-08-20 9:13 ` Julia Lawall
2013-08-20 16:26 ` Bjorn Helgaas
2013-08-20 16:26 ` Bjorn Helgaas
2013-08-20 16:26 ` Bjorn Helgaas
2013-08-20 18:53 ` Stephen Warren
2013-08-20 18:53 ` Stephen Warren
2013-08-20 19:31 ` Thierry Reding
2013-08-20 19:31 ` Thierry Reding
2013-08-20 19:31 ` Thierry Reding
2013-08-19 20:04 ` Bjorn Helgaas
2013-08-19 20:04 ` Bjorn Helgaas
2013-08-19 20:12 ` Thierry Reding
2013-08-19 20:12 ` Thierry Reding
2013-08-19 20:49 ` Bjorn Helgaas
2013-08-19 20:49 ` Bjorn Helgaas
2013-08-19 20:49 ` Bjorn Helgaas
2013-08-27 8:14 ` Thierry Reding
2013-08-27 8:14 ` Thierry Reding
2013-08-27 16:11 ` Stephen Warren
2013-08-27 16:11 ` Stephen Warren
2013-08-27 16:11 ` Stephen Warren
2013-08-27 18:03 ` Bjorn Helgaas
2013-08-27 18:03 ` Bjorn Helgaas
2013-08-27 18:03 ` Bjorn Helgaas
2013-08-28 13:02 ` Bjorn Helgaas
2013-08-28 13:02 ` Bjorn Helgaas
2013-08-28 13:27 ` Thierry Reding
2013-08-28 13:27 ` Thierry Reding
2013-08-28 13:27 ` Thierry Reding
2013-08-28 13:31 ` Thierry Reding
2013-08-28 13:31 ` Thierry Reding
2013-08-28 13:31 ` Thierry Reding
2013-08-19 11:20 ` [PATCH 2/7] serial: st-asc: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-19 11:20 ` [PATCH 3/7] iommu/arm: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-20 11:35 ` Will Deacon
2013-08-20 11:35 ` Will Deacon
2013-08-20 11:35 ` Will Deacon
2013-08-20 11:49 ` Julia Lawall
2013-08-20 11:49 ` Julia Lawall
2013-08-20 11:49 ` Julia Lawall
2013-08-19 11:20 ` [PATCH 4/7] dma: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-09-02 12:07 ` Vinod Koul
2013-09-02 12:19 ` Vinod Koul
2013-08-19 11:20 ` [PATCH 5/7] bcm63xx_enet: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-21 6:22 ` David Miller
2013-08-21 6:22 ` David Miller
2013-08-19 11:20 ` [PATCH 6/7] video: xilinxfb: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
2013-08-30 9:42 ` Tomi Valkeinen
2013-08-30 9:42 ` Tomi Valkeinen
2013-08-19 11:20 ` [PATCH 7/7] mmc: mvsdio: " Julia Lawall
2013-08-19 11:20 ` Julia Lawall
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=5212868D.2050604@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bhelgaas@google.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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 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.