From: David Brown <davidb@codeaurora.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] Move Qualcomm gpio drivers into drivers dir
Date: Fri, 27 May 2011 14:19:21 -0700 [thread overview]
Message-ID: <8yar57j6duu.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105271531200.3207@xanadu.home> (Nicolas Pitre's message of "Fri, 27 May 2011 15:31:47 -0400 (EDT)")
On Fri, May 27 2011, Nicolas Pitre wrote:
> 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?
They haven't been tested in linux-next for one, but more importantly, I
have to redo them to not include the msm-core changes that aren't going
to be going in.
I'm probably not going to be able to get to this until next week.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-05-27 21:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 21:50 [PATCH 0/7] Move Qualcomm gpio drivers into drivers dir David Brown
2011-05-18 21:50 ` [PATCH 1/7] msm: gpio: Remove unsupported devices David Brown
2011-05-18 21:50 ` [PATCH 2/7] msm: Remove chip-ifdefs for GPIO io mappings David Brown
2011-05-18 21:50 ` [PATCH 3/7] msm: gpio: Remove chip-specific register definitions David Brown
2011-05-18 21:50 ` [PATCH 4/7] msm: gpio: Remove ifdefs on gpio chip registers David Brown
2011-05-18 21:50 ` [PATCH 5/7] msm: gpiomux: Move public API to public header David Brown
2011-05-18 22:44 ` H Hartley Sweeten
2011-05-18 23:06 ` David Brown
2011-05-18 21:50 ` [PATCH 6/7] gpio_msm: Move Qualcomm v6 MSM driver into drivers David Brown
2011-05-18 21:50 ` [PATCH 7/7] gpio_msm: Move Qualcomm MSM v2 gpio " David Brown
2011-05-18 22:35 ` Stephen Boyd
2011-05-18 22:43 ` David Brown
2011-05-18 22:25 ` [PATCH 0/7] Move Qualcomm gpio drivers into drivers dir Linus Walleij
2011-05-19 19:34 ` Nicolas Pitre
2011-05-27 3:13 ` Grant Likely
2011-05-27 16:29 ` David Brown
2011-05-27 16:35 ` David Brown
2011-05-27 19:31 ` Nicolas Pitre
2011-05-27 21:19 ` David Brown [this message]
2011-06-03 22:44 ` [PATCH v2 " David Brown
2011-06-03 22:44 ` [PATCH v2 1/7] msm: gpio: Remove unsupported devices David Brown
2011-06-03 22:44 ` [PATCH v2 2/7] msm: Remove chip-ifdefs for GPIO io mappings David Brown
2011-06-03 22:44 ` [PATCH v2 3/7] msm: gpio: Remove chip-specific register definitions David Brown
2011-06-03 22:44 ` [PATCH v2 4/7] msm: gpio: Remove ifdefs on gpio chip registers David Brown
2011-06-03 22:44 ` [PATCH v2 5/7] msm: gpiomux: Move public API to public header David Brown
2011-06-03 22:44 ` [PATCH v2 6/7] gpio_msm: Move Qualcomm v6 MSM driver into drivers David Brown
2011-06-04 6:44 ` Grant Likely
2011-06-03 22:44 ` [PATCH v2 7/7] gpio_msm: Move Qualcomm MSM v2 gpio " David Brown
2011-06-04 6:45 ` Grant Likely
2011-06-04 0:15 ` [PATCH v2 0/7] Move Qualcomm gpio drivers into drivers dir David Brown
2011-06-06 21:51 ` [PATCH v3 0/8] " David Brown
2011-06-06 21:51 ` [PATCH v3 1/8] msm: gpio: Remove unsupported devices David Brown
2011-06-06 21:51 ` [PATCH v3 2/8] msm: Remove chip-ifdefs for GPIO io mappings David Brown
2011-06-06 21:51 ` [PATCH v3 3/8] msm: gpio: Remove chip-specific register definitions David Brown
2011-06-06 21:51 ` [PATCH v3 4/8] msm: gpio: Remove ifdefs on gpio chip registers David Brown
2011-06-06 21:51 ` [PATCH v3 5/8] msm: gpiomux: Move public API to public header David Brown
2011-06-06 21:51 ` [PATCH v3 6/8] msm: gpio: Fold register defs into C file David Brown
2011-06-06 21:51 ` [PATCH v3 7/8] gpio_msm: Move Qualcomm v6 MSM driver into drivers David Brown
2011-06-06 21:51 ` [PATCH v3 8/8] gpio_msm: Move Qualcomm MSM v2 gpio " David Brown
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=8yar57j6duu.fsf@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=tglx@linutronix.de \
/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).