From: Linus Walleij <linus.walleij@linaro.org>
To: Grant Likely <grant.likely@secretlab.ca>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Lee Jones <lee.jones@linaro.org>,
H Hartley Sweeten <hartleys@visionengravers.com>
Subject: Re: [PATCH 00/19] GPIO exodus and cleanup
Date: Mon, 22 Aug 2011 09:53:48 +0200 [thread overview]
Message-ID: <CACRpkdbPFuFHBuHzO2bP+z=za2kOFk4AZdgMVy=U6kcMmw9LSw@mail.gmail.com> (raw)
In-Reply-To: <CACxGe6tEOnUzFjKMqNfp10b8SyuJDDFzg0eiPzhKNNCY55LECw@mail.gmail.com>
On Sun, Aug 21, 2011 at 9:09 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Aug 19, 2011 at 5:45 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> 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.
Okay! Russell I've put them into your patch tracker as patches
7032/1 thru 7050/1 so you can pick and choose. I've rebased on
top of what's in -next hoping that the stuff there affecting these
file will mainly be identical to what's on your "gpio" branch.
Tell me if I should rebase on something specific or if there are
any problems.
Once this lands in -next I will take another round over arch/arm/*
and see if I can find more movement/split/cleanup items like these.
Thanks,
Linus Walleij
next prev parent reply other threads:[~2011-08-22 7:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 12:16 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
2011-08-22 7:53 ` Linus Walleij [this message]
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='CACRpkdbPFuFHBuHzO2bP+z=za2kOFk4AZdgMVy=U6kcMmw9LSw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=hartleys@visionengravers.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®