From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: Jarkko Nikula <jarkko.nikula@nokia.com>, linux-omap@vger.kernel.org
Subject: Re: [RFC 0/21 Continue phasing out legacy GPIO calls
Date: Thu, 30 Oct 2008 10:32:16 -0700 [thread overview]
Message-ID: <20081030173215.GU13227@atomide.com> (raw)
In-Reply-To: <200810300043.07813.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [081030 00:43]:
> On Wednesday 29 October 2008, Tony Lindgren wrote:
> > Let's do the clean-up patches in two phases, one series that
> > applies against the mainline kernel, then additional patches for
> > linux-omap. Otherwise we'll never get out of this merge hell.
>
> Note that the patches I sent were in two phases ... but the
> other way around. The OMAP-only patches can go in immediately,
> and won't change anything of node.
OK, thanks.
> But since the ones that "also" apply against mainline remove
> the legacy calls, they need to go later. If it were realistic
> to merge them for 2.6.28, they could safely be pulled down IFF
> the OMAP-only patches were already in the OMAP tree.
Great, to me those look safe to merge. Can you Cc Russell on the
arch/arm/*omap* patches if you merge them via gpiolib patches?
Basically anything that will cause merge conflicts for omap-all
should go via Russell so we don't frustrate him further, but
I don't think these will cause an issue for him.
Tony
next prev parent reply other threads:[~2008-10-30 17:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 11:36 [RFC 0/21 Continue phasing out legacy GPIO calls Jarkko Nikula
2008-10-29 11:36 ` [RFC 01/21] ARM: OMAP: Clean-up OMAP GPIO request/free functions Jarkko Nikula
2008-10-29 17:49 ` David Brownell
2008-10-30 12:58 ` Jarkko Nikula
2008-10-30 16:55 ` David Brownell
2008-10-29 11:36 ` [RFC 02/21] OneNAND OMAP2: Complete gpiolib conversion Jarkko Nikula
2008-10-29 11:36 ` [RFC 03/21] SPI: TSC2301: " Jarkko Nikula
2008-10-29 11:36 ` [RFC 04/21] ARM: OMAP: Complete LCD panel " Jarkko Nikula
2008-10-29 11:36 ` [RFC 05/21] Complete brf6150 and hci_h4p " Jarkko Nikula
2008-10-29 11:36 ` [RFC 06/21] CBUS: Complete " Jarkko Nikula
2008-10-29 11:36 ` [RFC 07/21] INPUT: TSC2005: " Jarkko Nikula
2008-10-29 11:36 ` [RFC 08/21] INPUT: TS_Hx: " Jarkko Nikula
2008-10-29 11:36 ` [RFC 09/21] OMAP: USB: " Jarkko Nikula
2008-10-29 11:36 ` [RFC 10/21] LEDS: Complete leds-omap gpiolib conversion and do some fixes Jarkko Nikula
2008-10-29 17:15 ` David Brownell
2008-10-29 11:36 ` [RFC 11/21] ARM: OMAP: Complete N8x0 board file gpiolib conversion Jarkko Nikula
2008-10-29 11:36 ` [RFC 12/21] ARM: OMAP: Complete TUSB-OMAP interface " Jarkko Nikula
2008-10-29 11:36 ` [RFC 13/21] ARM: OMAP: Complete OMAP1 board files " Jarkko Nikula
2008-10-29 11:36 ` [RFC 14/21] ARM: OMAP: Complete 3430sdp board file " Jarkko Nikula
2008-10-29 11:36 ` [RFC 15/21] ARM: OMAP: Complete omap3evm " Jarkko Nikula
2008-10-29 11:36 ` [RFC 16/21] ARM: OMAP2: Complete gpiolib conversion in upstream merged board files Jarkko Nikula
2008-10-29 11:36 ` [RFC 17/21] ARM: OMAP: Complete gpio-switch gpiolib conversion Jarkko Nikula
2008-10-29 11:36 ` [RFC 18/21] ARM: OMAP: Complete OMAP1 serial.c " Jarkko Nikula
2008-10-29 11:36 ` [RFC 19/21] ARM: OMAP: LEDS: Complete " Jarkko Nikula
2008-10-29 17:46 ` David Brownell
2008-10-30 13:01 ` Jarkko Nikula
2008-10-29 11:36 ` [RFC 20/21] ARM: OMAP: Complete Innovator FPGA " Jarkko Nikula
2008-10-29 11:36 ` [RFC 21/21] ARM: OMAP: Complete debug board " Jarkko Nikula
2008-10-29 17:19 ` David Brownell
2008-10-29 16:00 ` [RFC 0/21 Continue phasing out legacy GPIO calls Tony Lindgren
2008-10-29 23:49 ` David Brownell
2008-10-30 17:26 ` Tony Lindgren
2008-10-30 7:43 ` David Brownell
2008-10-30 17:32 ` Tony Lindgren [this message]
2008-10-30 18:16 ` David Brownell
2008-10-30 18:21 ` Tony Lindgren
2008-10-30 13:11 ` Jarkko Nikula
2008-10-30 17:34 ` Tony Lindgren
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=20081030173215.GU13227@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.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