From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [OMAP tree][RFC 2.6.28-rc2-omap 0/9]
Date: Fri, 21 Nov 2008 14:18:52 -0800 [thread overview]
Message-ID: <20081121221852.GF4927@atomide.com> (raw)
In-Reply-To: <1225455537-14017-1-git-send-email-jarkko.nikula@nokia.com>
* Jarkko Nikula <jarkko.nikula@nokia.com> [081031 05:20]:
> This is from the "Continue phasing out legacy GPIO calls" set I sent earlier
> and include files which are in linux-omap tree only.
>
> This is generated on top of David's recent 4+5 "legacy gpio phaseout.." patches
> in linux-omap tree.
>
> Note that this still includes the drivers/leds/leds-omap.c which should vanish
> and board-palmtt.c which should be converted to use leds-gpio.c instead.
Pushing this series to l-o tree.
Tony
prev parent reply other threads:[~2008-11-21 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 12:18 [OMAP tree][RFC 2.6.28-rc2-omap 0/9] Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 1/9] USB: EHCI-OMAP: Switch to gpio_request/free calls Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 2/9] ARM: OMAP: Switch to gpio_request/free calls (part 2) Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 3/9] ARM: OMAP: Switch OMAP LCD panels to use gpio_request/free calls Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 4/9] SPI: TSC2301: Switch to " Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 5/9] [Bluetooth] Switch brf6150 and hci_h4p to use " Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 6/9] CBUS: Switch to " Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 7/9] INPUT: TSC2005: " Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 8/9] INPUT: TS_Hx: " Jarkko Nikula
2008-10-31 12:18 ` [OMAP tree][RFC 2.6.28-rc2-omap 9/9] LEDS: Switch leds-omap to use " Jarkko Nikula
2008-11-21 22:18 ` Tony Lindgren [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=20081121221852.GF4927@atomide.com \
--to=tony@atomide.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.