From: Kevin Hilman <khilman@linaro.org>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"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 07:50:13 -0800 [thread overview]
Message-ID: <87iotl453e.fsf@linaro.org> (raw)
In-Reply-To: <52D69551.4070607@ti.com> (Sekhar Nori's message of "Wed, 15 Jan 2014 19:34:01 +0530")
Sekhar Nori <nsekhar@ti.com> writes:
> On Wednesday 15 January 2014 07:21 PM, Linus Walleij wrote:
>> On Wed, Jan 15, 2014 at 1:54 PM, Sekhar Nori <nsekhar@ti.com> wrote:
>>> On Wednesday 15 January 2014 02:58 PM, Linus Walleij wrote:
>>
>>>> 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.
>>
>> But as it is a fix I believe the ARM SoC maintainers will apply it
>> directly to the davinci branch.
>
> Sorry I did not realize this is a fix.
>
>>
>> Wolfram: I suggest you send this patch with my ACK directly
>> to arm@kernel.org and ask it to be applied to the davinci branch
>> in the ARM SoC tree.
>
> This would work too, I guess. Wolfram, can you please keep me in CC too
> in case questions/actions come up?
Sekhar, I assume this is an ack from you too? If so, Wolfram, please
include that in the patch submitted to arm-soc.
Kevin
next prev parent reply other threads:[~2014-01-15 15:50 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
2014-01-15 13:51 ` Linus Walleij
2014-01-15 14:04 ` Sekhar Nori
2014-01-15 15:50 ` Kevin Hilman [this message]
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=87iotl453e.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--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).