Thread (3 messages) 3 messages, 3 authors, 2012-03-13
DORMANTno replies
Revisions (9)
  1. v1 [diff vs current]
  2. v2 [diff vs current]
  3. v3 [diff vs current]
  4. v3 [diff vs current]
  5. v3 [diff vs current]
  6. v3 [diff vs current]
  7. v3 current
  8. v4 [diff vs current]
  9. v4 [diff vs current]

[PATCH v3 00/13] gpio/omap: Some more driver cleanup and fixes

From: DebBarma, Tarun Kanti <hidden>
Date: 2012-03-13 04:35:41
Also in: linux-omap

Possibly related (same subject, not in this thread)

On Tue, Mar 13, 2012 at 9:27 AM, Grant Likely [off-list ref] wrote:
On Mon, 12 Mar 2012 15:28:42 -0700, Kevin Hilman [off-list ref] wrote:
quoted
"DebBarma, Tarun Kanti" [off-list ref] writes:

[...]
quoted
quoted
quoted
Oops... I am sorry.
I was in the process of updating the branch with latest comments after
base-lining on Grant's:
git://git.secretlab.ca/git/linux-2.6.git
Branch: gpio/next
Because this has all the gpio changes including Benoit's latest gpio
devicetree changes.
Should I go ahead?
Anyways, for the time being I am updating on top of your changes as before.
You should be able to see the branch shortly.
Please note that the branch has your following patch:
gpio/omap: fix wakeups on level-triggered GPIOs
Please be sure to Cc the GPIO maintainer (added now.)
Sure.
quoted
Grant can we consider your gpio/next a stable baseline for further
GPIO fixes?

If so, Tarun, please base your branch there. ?Otherwise, continue to use
my for_3.4/gpio/runtime-pm-cleanup, but please test it by merging with
the gpio/next branch.
I'm not going to rebase gpio/next before the merge window; you can base on it with
confidence.
I will base and start doing the tests.
In the mean time I will wait for Kevin's comments on the series.
Thanks.
--
Tarun
g.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help