From: Sekhar Nori <nsekhar@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
Kevin Hilman <khilman@linaro.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 7/7] drivers/gpio: don't check resource with devm_ioremap_resource
Date: Wed, 15 Jan 2014 18:24:01 +0530 [thread overview]
Message-ID: <52D684E9.6080308@ti.com> (raw)
In-Reply-To: <CACRpkdYymB4i7Ju5MMNXWVe5nB6_NbWHwrPbOK2KeT0Ji-RzQg@mail.gmail.com>
On Wednesday 15 January 2014 02:58 PM, Linus Walleij wrote:
> On Tue, Jan 14, 2014 at 12:58 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
>
>> devm_ioremap_resource does sanity checks on the given resource. No need to
>> duplicate this in the driver.
>>
>> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
>> ---
>>
>> Should go via subsystem tree
>>
>> drivers/gpio/gpio-davinci.c | 5 -----
>> 1 file changed, 5 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio-davinci.c
>> index 84be701..a5e1a56 100644
>> --- a/drivers/gpio/gpio-davinci.c
>> +++ b/drivers/gpio/gpio-davinci.c
>> @@ -172,11 +172,6 @@ static int davinci_gpio_probe(struct platform_device *pdev)
>> }
>>
>> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> - if (!res) {
>> - dev_err(dev, "Invalid memory resource\n");
>> - return -EBUSY;
>> - }
>> -
>> gpio_base = devm_ioremap_resource(dev, res);
>> if (IS_ERR(gpio_base))
>> return PTR_ERR(gpio_base);
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> The DaVinci maintainers are queuing GPIO patches for their driver
> for this merge window, so requesting them to apply this patch.
I wont be sending any more pull requests for v3.14. Even if I send, the
ARM-SoC maintainers will not take it anyway. So likely this wont get
into v3.14. For v3.15, Linus should be able to queue it as dependencies
would have made it into the kernel by then.
Thanks,
Sekhar
next prev parent reply other threads:[~2014-01-15 12:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 11:58 [PATCH 1/7] arch/mips/lantiq/xway: don't check resource with devm_ioremap_resource Wolfram Sang
2014-01-14 11:58 ` [PATCH 2/7] drivers/amba: " Wolfram Sang
2014-01-14 13:32 ` Thierry Reding
2014-01-14 17:40 ` Stephen Warren
2014-01-14 18:30 ` Wolfram Sang
2014-02-05 17:18 ` Stephen Warren
2014-01-14 11:58 ` [PATCH 3/7] drivers/gpu/host1x/drm: " Wolfram Sang
2014-01-14 13:40 ` Thierry Reding
2014-01-14 11:58 ` [PATCH 4/7] drivers/pci/host: " Wolfram Sang
2014-01-14 13:17 ` Marek Vasut
2014-01-14 22:32 ` Jingoo Han
2014-01-14 11:58 ` [PATCH 5/7] drivers/usb/dwc3: " Wolfram Sang
2014-01-14 14:15 ` Felipe Balbi
2014-01-14 11:58 ` [PATCH 6/7] arch/mips/pci: " Wolfram Sang
2014-01-14 11:58 ` [PATCH 7/7] drivers/gpio: " Wolfram Sang
2014-01-15 9:28 ` Linus Walleij
2014-01-15 12:54 ` Sekhar Nori [this message]
2014-01-15 13:51 ` Linus Walleij
2014-01-15 14:04 ` Sekhar Nori
2014-01-15 15:50 ` Kevin Hilman
2014-01-16 4:29 ` Sekhar Nori
2014-02-03 11:30 ` Grygorii Strashko
2014-01-14 12:03 ` [PATCH 1/7] arch/mips/lantiq/xway: " John Crispin
2014-01-14 12:11 ` Wolfram Sang
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=52D684E9.6080308@ti.com \
--to=nsekhar@ti.com \
--cc=gnurou@gmail.com \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=wsa@the-dreams.de \
/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).