From: Grant Likely <grant.likely@secretlab.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Shawn Guo <shawn.guo@linaro.org>,
linux-kernel@vger.kernel.org, arnd@arndb.de,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
patches@linaro.org
Subject: Re: [PATCH v2 0/2] Move Freescale MXS gpio driver into drivers/gpio
Date: Fri, 3 Jun 2011 11:57:23 -0600 [thread overview]
Message-ID: <20110603175723.GE15616@ponder.secretlab.ca> (raw)
In-Reply-To: <20110530064502.GC23771@pengutronix.de>
On Mon, May 30, 2011 at 08:45:02AM +0200, Sascha Hauer wrote:
> Grant,
>
> I suppose we should take this through the architecture tree. Can I have
> your Ack for this?
>
Actually, as mentioned in my other email, I'd like to see this series
respun with a separate patch for just moving the gpio driver (without
breaking the build).
Also, I've been thinking about how to merge these changes, and I'd
rather take them through the gpio tree since there will be a lot of
conflicts with the other gpio driver moves. It will be easier to
resolve merge conflicts if I push it out to my tree and allow the
subarch trees to merge in mine if necessary.
g.
prev parent reply other threads:[~2011-06-03 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 15:09 Shawn Guo
2011-05-28 15:09 ` [PATCH v2 1/2] gpio: gpio-mxs: add gpio driver for Freescale MXS architecture Shawn Guo
2011-05-28 15:09 ` [PATCH v2 2/2] ARM: mxs: use gpio-mxs driver by adding platform device Shawn Guo
2011-05-29 19:16 ` Arnd Bergmann
2011-05-30 6:45 ` [PATCH v2 0/2] Move Freescale MXS gpio driver into drivers/gpio Sascha Hauer
2011-06-03 17:57 ` Grant Likely [this message]
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=20110603175723.GE15616@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=arnd@arndb.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.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
all inboxes | Powered by JetHome®