From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/1] dying serial console in PM branch
Date: Mon, 19 Oct 2009 16:02:41 -0700 [thread overview]
Message-ID: <20091019230241.GV12576@atomide.com> (raw)
In-Reply-To: <1255990482-16201-1-git-send-email-khilman@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [091019 15:14]:
> This patch fixes the problems in the PM branch where the serial
> console on UART3 was not able to wakeup after the inactivity timer.
>
> This fix has been pushed to the PM branch already, but should also
> be queued as a fix upstream.
OK, good to hear you found the problem!
> Tony, this is available in my pm-upstream/pm-fixes-32 branch based at
> v2.6.32-rc5. I shouldn't have any more PM fixes coming for 2.6.32.
Thanks, since it's just one patch, I'll apply it into my omap-fixes
from the patchwork.k.o for easier handling.
Regards,
Tony
>
> Kevin Hilman (1):
> OMAP3: PM: enable UART3 module wakeups
>
> arch/arm/mach-omap2/pm34xx.c | 7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-10-19 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 22:14 [PATCH 0/1] dying serial console in PM branch Kevin Hilman
2009-10-19 22:14 ` [PATCH 1/1] OMAP3: PM: enable UART3 module wakeups Kevin Hilman
2009-10-19 23:04 ` [APPLIED] " Tony Lindgren
2009-10-19 23:02 ` 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=20091019230241.GV12576@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--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