From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP3+: PRM/hwmod: fix and improve I/O chain wakeup support
Date: Wed, 9 May 2012 13:13:35 +0300 [thread overview]
Message-ID: <1336558415.2149.274.camel@sokoban> (raw)
In-Reply-To: <20120420165508.GD21106@atomide.com>
On Fri, 2012-04-20 at 09:55 -0700, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [120420 01:24]:
> > Hi,
> >
> > What happened with this pull request? It doesn't seem to be in 3.4 at
> > least.
>
> There was a boot issue on omap3 evm and that branch got dropped.
> Will merge it again after Paul has figured out the issue.
Paul / Tony, do you want me to re-send the set for this with the OMAP3
EVM related fix? This was figured out in a separate email chain.
-Tero
next prev parent reply other threads:[~2012-05-09 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 10:15 [GIT PULL] ARM: OMAP3+: PRM/hwmod: fix and improve I/O chain wakeup support Paul Walmsley
2012-04-20 8:21 ` Tero Kristo
2012-04-20 16:55 ` Tony Lindgren
2012-05-09 10:13 ` Tero Kristo [this message]
2012-05-10 17:26 ` Paul Walmsley
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=1336558415.2149.274.camel@sokoban \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).