From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add GPIO driver for Allwinner SoCs
Date: Sat, 12 Jan 2013 09:54:17 +0100 [thread overview]
Message-ID: <50F124B9.30000@free-electrons.com> (raw)
In-Reply-To: <CACRpkdZQAim4_3E6RG=d4pJi80B6W-xzW7n=Od86VJNcPO4FVw@mail.gmail.com>
On 10/01/2013 12:13, Linus Walleij wrote:
> On Sat, Jan 5, 2013 at 4:35 PM, Olof Johansson <olof@lixom.net> wrote:
>
>> I haven't looked closely at the patch yet, but this is a case where it
>> makes sense to merge the gpio/pinctrl patch through Linus/Grant's
>> tree, and merge the dtsi update through arm-soc -- while you need
>> both, nothing is broken by having just one or the other, so taking the
>> separate merge paths are fine.
>>
>> Linus, Grant, sound ok to you?
>
> Sure. But I have requested a few changes to the patch set...
And we need to merge the pinctrl patches first also.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@stericsson.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 0/2] Add GPIO driver for Allwinner SoCs
Date: Sat, 12 Jan 2013 09:54:17 +0100 [thread overview]
Message-ID: <50F124B9.30000@free-electrons.com> (raw)
In-Reply-To: <CACRpkdZQAim4_3E6RG=d4pJi80B6W-xzW7n=Od86VJNcPO4FVw@mail.gmail.com>
On 10/01/2013 12:13, Linus Walleij wrote:
> On Sat, Jan 5, 2013 at 4:35 PM, Olof Johansson <olof@lixom.net> wrote:
>
>> I haven't looked closely at the patch yet, but this is a case where it
>> makes sense to merge the gpio/pinctrl patch through Linus/Grant's
>> tree, and merge the dtsi update through arm-soc -- while you need
>> both, nothing is broken by having just one or the other, so taking the
>> separate merge paths are fine.
>>
>> Linus, Grant, sound ok to you?
>
> Sure. But I have requested a few changes to the patch set...
And we need to merge the pinctrl patches first also.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-12 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 16:45 [PATCH 0/2] Add GPIO driver for Allwinner SoCs Maxime Ripard
2013-01-04 16:45 ` Maxime Ripard
2013-01-04 16:45 ` [PATCH 1/2] ARM: sunxi: gpio: Add Allwinner SoCs GPIO drivers Maxime Ripard
2013-01-04 16:45 ` Maxime Ripard
2013-01-10 11:06 ` Linus Walleij
2013-01-10 11:06 ` Linus Walleij
2013-01-12 9:06 ` Maxime Ripard
2013-01-12 9:06 ` Maxime Ripard
2013-01-17 11:06 ` Linus Walleij
2013-01-17 11:06 ` Linus Walleij
2013-01-04 16:45 ` [PATCH 2/2] ARM: sunxi: Add the GPIOs node to the device tree Maxime Ripard
2013-01-04 16:45 ` Maxime Ripard
2013-01-05 15:35 ` [PATCH 0/2] Add GPIO driver for Allwinner SoCs Olof Johansson
2013-01-05 15:35 ` Olof Johansson
2013-01-10 11:13 ` Linus Walleij
2013-01-10 11:13 ` Linus Walleij
2013-01-12 8:54 ` Maxime Ripard [this message]
2013-01-12 8:54 ` Maxime Ripard
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=50F124B9.30000@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.