From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] add gpio driver gpio-mxs
Date: Fri, 20 May 2011 13:25:25 +0200 [thread overview]
Message-ID: <20110520112524.GC10403@pengutronix.de> (raw)
In-Reply-To: <20110520102410.GD27251@S2100-06.ap.freescale.net>
On Fri, May 20, 2011 at 06:24:11PM +0800, Shawn Guo wrote:
> On Fri, May 20, 2011 at 12:02:42PM +0200, Sascha Hauer wrote:
> > Hi Shawn,
> >
> Hi Sascha,
>
> > On Fri, May 20, 2011 at 05:51:25PM +0800, Shawn Guo wrote:
> > > The patch set is to move Freescale MXS gpio driver from mach-mxs
> > > into drivers/gpio. Different from u300 gpio driver that all gpio
> > > ports are registered as one device, gpio-mxs expects every single
> > > port is a gpio device.
> > >
> > > The first 3 patches are just to ease review and can be squashed into
> > > the last one.
> > >
> > > Shawn Guo (4):
> > > gpio: gpio-mxs: add file gpio-mxs.c
> > > gpio: gpio-mxs: drop mach-specific accessors
> > > gpio: gpio-mxs: remove gpio port definition and registration
> > > gpio: gpio-mxs: add gpio driver for Freescale MXS architecture
> >
> > Your series should be bisectible. So please either:
> >
> > - Add the driver the way you want it (no need to modify a new file in
> > four steps)
>
> As I said above, I split it into 4 patches just to ease the review,
> and they can be squashed into one when applying.
>
> > - atomically switch to the new driver
> > - remove old driver
> >
> These two steps happened in the patch set '[PATCH 0/3] remove mach-mxs
> gpio driver'. The patch order should be reworked though.
>
> BTW, are you looking at moving plat-mxc/gpio.c, or I can give a hand
> there?
I'm not working on this, go ahead.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-05-20 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 9:51 [PATCH 0/4] add gpio driver gpio-mxs Shawn Guo
2011-05-20 9:51 ` [PATCH 1/4] gpio: gpio-mxs: add file gpio-mxs.c Shawn Guo
2011-05-20 9:51 ` [PATCH 2/4] gpio: gpio-mxs: drop mach-specific accessors Shawn Guo
2011-05-20 9:51 ` [PATCH 3/4] gpio: gpio-mxs: remove gpio port definition and registration Shawn Guo
2011-05-20 9:51 ` [PATCH 4/4] gpio: gpio-mxs: add gpio driver for Freescale MXS architecture Shawn Guo
2011-05-20 11:24 ` Sascha Hauer
2011-05-20 14:31 ` Shawn Guo
2011-05-20 10:02 ` [PATCH 0/4] add gpio driver gpio-mxs Sascha Hauer
[not found] ` <20110520102410.GD27251@S2100-06.ap.freescale.net>
2011-05-20 11:25 ` Sascha Hauer [this message]
2011-05-27 3:15 ` Grant Likely
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=20110520112524.GC10403@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).