public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: l-o <linux-omap@vger.kernel.org>,
	l-a <linux-arm-kernel@lists.infradead.org>,
	Tony <tony@atomide.com>, Koen Kooi <koen@beagleboard.org>
Subject: Re: [PATCH v3 0/3] OMAP3: beaglexm: GPIO fixes
Date: Thu, 06 Jan 2011 14:15:23 -0800	[thread overview]
Message-ID: <8739p5u1ac.fsf@ti.com> (raw)
In-Reply-To: <1294343679-10605-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Thu, 6 Jan 2011 13:54:36 -0600")

Nishanth Menon <nm@ti.com> writes:

> Hi,
> As discussed in the threads:
> http://thread.gmane.org/gmane.linux.ports.arm.omap/47807/
> http://marc.info/?t=121540030800004&r=1&w=2
>
> here is the split up series with commit message after discussion:
> http://www.beagleboard.org/irclogs/index.php?date=2011-01-06#T19:12:21
>
> Koen Kooi (3):
>   omap3: beaglexm: fix EHCI power up GPIO dir
>   omap3: beaglexm: fix DVI reset GPIO
>   omap3: beaglexm: power on DVI
>
>  arch/arm/mach-omap2/board-omap3beagle.c |   37 ++++++++++++++++++++++++++----
>  1 files changed, 32 insertions(+), 5 deletions(-)
>
> v3:
> 	split up the series, addressed review comments

Thanks, queueing for the .38-rc cycle.

Kevin

> v2: http://marc.info/?t=129276977900002&r=1&w=2
> 	Reenable the PMU stat LED
> v1: http://marc.info/?t=129172571000001&r=1&w=2
>
> Regards,
> Nishanth Menon

      parent reply	other threads:[~2011-01-06 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 19:54 [PATCH v3 0/3] OMAP3: beaglexm: GPIO fixes Nishanth Menon
2011-01-06 19:54 ` [PATCH v3 1/3] omap3: beaglexm: fix EHCI power up GPIO dir Nishanth Menon
2011-01-06 19:54 ` [PATCH v3 2/3] omap3: beaglexm: fix DVI reset GPIO Nishanth Menon
2011-01-06 19:54 ` [PATCH v3 3/3] omap3: beaglexm: power on DVI Nishanth Menon
2011-01-06 19:57 ` [PATCH v3 0/3] OMAP3: beaglexm: GPIO fixes Koen Kooi
2011-01-06 22:15 ` Kevin Hilman [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=8739p5u1ac.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=koen@beagleboard.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=tony@atomide.com \
    /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