From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.28-rc2-omap 0/5] legacy gpio phaseout (II) ...
Date: Thu, 13 Nov 2008 13:39:15 -0800 [thread overview]
Message-ID: <20081113213914.GF3106@atomide.com> (raw)
In-Reply-To: <200810300031.42711.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [081030 00:38]:
> Second set, plus the first of Jarkko's:
>
> - OMAP tree
> * use gpio_direction_output()
> * use gpio_to_irq()
> - Mainline *and* OMAP trees:
> * use gpio_direction_output(), remove the legacy version
> * use gpio_to_irq()
> * make legacy gpio_request()/gpio_free() calls superfluous
>
> These go on top of the preceding four.
>
> Merging these will facilitate for example a mach-omap2/gpio.c file
> that is much nicer since it's not full of OMAP1 support...
Pushing today and adding to omap-upstream queue.
Tony
prev parent reply other threads:[~2008-11-13 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 7:31 [patch 2.6.28-rc2-omap 0/5] legacy gpio phaseout (II) David Brownell
2008-11-13 21:39 ` 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=20081113213914.GF3106@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--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