linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/19] GPIO exodus and cleanup
Date: Sun, 21 Aug 2011 00:09:53 -0700	[thread overview]
Message-ID: <CACxGe6tEOnUzFjKMqNfp10b8SyuJDDFzg0eiPzhKNNCY55LECw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYw96QD0sGOhA=osKYbnD6=MTqiAF=m5++BjM-s1Mn--w@mail.gmail.com>

On Fri, Aug 19, 2011 at 5:45 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Wed, Aug 17, 2011 at 11:37 AM, Linus Walleij
> <linus.walleij@linaro.org> wrote:
>> On Wed, Aug 17, 2011 at 11:01 AM, Russell King - ARM Linux
>> <linux@arm.linux.org.uk> wrote:
>>> On Wed, Aug 10, 2011 at 02:16:04PM +0200, Linus Walleij wrote:
>>>> The following patch set is rebased on top of Russell's
>>>> 13 cleanup patches and can be finalized as soon as there
>>>> is a branch in RMKs tree that can accumulate this work.
>>>
>>> If Grant acks the relevant ones, they can go to the patch system and
>>> merged into that branch.
>>
>> Thanks that'd be smooth.
>>
>> Grant can you N/ACK the patches you consider relevant for
>> the GPIO subsystem?
>
> Ping on this, on monday I'll pretend it's no big deal and pour them
> into Russells patch tracker anyway, since he's managing more than
> half of the kernels GPIO code in arch/arm/* anyway.

If Russell is okay with it, then go ahead and merge it.  I'm being
pretty liberal about GPIO driver moves.  I'm fine with them getting
cleaned up after the drivers/gpio move.

g.

  reply	other threads:[~2011-08-21  7:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 12:16 [PATCH 00/19] GPIO exodus and cleanup Linus Walleij
2011-08-17  9:01 ` Russell King - ARM Linux
2011-08-17  9:37   ` Linus Walleij
2011-08-19 12:45     ` Linus Walleij
2011-08-21  7:09       ` Grant Likely [this message]
2011-08-22  7:53         ` Linus Walleij
2011-08-22  8:27           ` Russell King - ARM Linux
2011-08-22  9:24             ` Russell King - ARM Linux
2011-08-22  9:48               ` Linus Walleij
2011-08-22  9:48             ` Linus Walleij

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=CACxGe6tEOnUzFjKMqNfp10b8SyuJDDFzg0eiPzhKNNCY55LECw@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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 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).