From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: l-o <linux-omap@vger.kernel.org>,
l-a <linux-arm-kernel@lists.infradead.org>,
Kevin <khilman@ti.com>, Koen Kooi <koen@beagleboard.org>,
Aaro <aaro.koskinen@nokia.com>
Subject: Re: [PATCH v4 0/3] OMAP3: beaglexm: GPIO fixes
Date: Mon, 10 Jan 2011 11:04:37 -0800 [thread overview]
Message-ID: <20110110190436.GE4957@atomide.com> (raw)
In-Reply-To: <1294441282-17986-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [110107 15:00]:
> 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: fix power on of DVI
Dropping the earlier versions from omap-fixes, I want to get the
build fixes in ASAP. These can wait a bit until Aaro's comments
are addressed.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] OMAP3: beaglexm: GPIO fixes
Date: Mon, 10 Jan 2011 11:04:37 -0800 [thread overview]
Message-ID: <20110110190436.GE4957@atomide.com> (raw)
In-Reply-To: <1294441282-17986-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [110107 15:00]:
> 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: fix power on of DVI
Dropping the earlier versions from omap-fixes, I want to get the
build fixes in ASAP. These can wait a bit until Aaro's comments
are addressed.
Regards,
Tony
next prev parent reply other threads:[~2011-01-10 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH v3 0/3] OMAP3: beaglexm: GPIO fixes>
2011-01-07 23:01 ` [PATCH v4 0/3] OMAP3: beaglexm: GPIO fixes Nishanth Menon
2011-01-07 23:01 ` Nishanth Menon
2011-01-07 23:17 ` Kevin Hilman
2011-01-07 23:17 ` Kevin Hilman
2011-01-10 19:04 ` Tony Lindgren [this message]
2011-01-10 19:04 ` Tony Lindgren
2011-01-10 19:13 ` Nishanth Menon
2011-01-10 19:13 ` Nishanth Menon
2011-01-07 23:01 ` [PATCH v4 1/3] omap3: beaglexm: fix EHCI power up GPIO dir Nishanth Menon
2011-01-07 23:01 ` Nishanth Menon
2011-01-10 12:44 ` Aaro Koskinen
2011-01-10 12:44 ` Aaro Koskinen
2011-01-10 14:23 ` Nishanth Menon
2011-01-10 14:23 ` Nishanth Menon
2011-01-07 23:01 ` [PATCH v4 2/3] omap3: beaglexm: fix DVI reset GPIO Nishanth Menon
2011-01-07 23:01 ` Nishanth Menon
2011-01-07 23:01 ` [PATCH v4 3/3] omap3: beaglexm: fix power on of DVI Nishanth Menon
2011-01-07 23:01 ` Nishanth Menon
2011-01-10 12:51 ` Aaro Koskinen
2011-01-10 12:51 ` Aaro Koskinen
2011-01-10 14:34 ` Nishanth Menon
2011-01-10 14:34 ` Nishanth Menon
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=20110110190436.GE4957@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@nokia.com \
--cc=khilman@ti.com \
--cc=koen@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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 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.