[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.1105271531200.3207@xanadu.home>
Date: Fri, 27 May 2011 15:31:47 -0400 (EDT)
From: Nicolas Pitre <nico@...xnic.net>
To: David Brown <davidb@...eaurora.org>
Cc: Grant Likely <grant.likely@...retlab.ca>,
Daniel Walker <dwalker@...o99.com>,
Bryan Huntsman <bryanh@...eaurora.org>,
Russell King <linux@....linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/7] Move Qualcomm gpio drivers into drivers dir
On Fri, 27 May 2011, David Brown wrote:
> On Fri, May 27 2011, David Brown wrote:
>
> > On Thu, May 26 2011, Grant Likely wrote:
> >
> >> On Wed, May 18, 2011 at 02:50:46PM -0700, David Brown wrote:
> >>> This patch series moves the Qualcomm MSM gpio device drivers into the
> >>> drivers/gpio directory.
> >>>
> >>> The MSM's have two flavors of gpio driver. The one for the newer
> >>> v7-based chips is a bit cleaner, and can just be moved. The one for
> >>> the older v6-based chips took some cleanup to get rid of numerous
> >>> ifdefs based on the particular machine. Both drivers can now be
> >>> selected and will be used on appropriate targets.
> >>>
> >>> There is still a minor entanglement with the MSM-specific gpiomux
> >>> code. This will be cleaned up as MSM moves to use pinmux.
> >>>
> >>> David Brown (7):
> >>> msm: gpio: Remove unsupported devices
> >>> msm: Remove chip-ifdefs for GPIO io mappings
> >>> msm: gpio: Remove chip-specific register definitions
> >>> msm: gpio: Remove ifdefs on gpio chip registers
> >>> msm: gpiomux: Move public API to public header
> >>> gpio_msm: Move Qualcomm v6 MSM driver into drivers
> >>> gpio_msm: Move Qualcomm MSM v2 gpio driver into drivers
> >>
> >> What's the status of this series. I only got cc'd on the last two
> >> patches; did you want me to pick up the whole lot, or is it being
> >> merged via the msm tree?
> >
> > Let me send out an update, incorporating the suggestions. I need to
> > rebase these changes off of the current MSM code, since the msm-next
> > tree contains changes that aren't going into the merge window because of
> > extra ARM scrutiny.
> >
> >> Alternately, if there is a git branch with these patches in it, then I
> >> can merge that instead of applying individually.
> >
> > I'll send you a pull request after I send out the updates.
>
> Oh, and in case it isn't clear, I wasn't expecting these to make it into
> this merge window.
Why not?
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists