From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] OMAP PM fixes for 2.6.32
Date: Mon, 05 Oct 2009 10:57:10 -0700 [thread overview]
Message-ID: <877hv9yb9l.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1254507295-11381-1-git-send-email-khilman@deeprootsystems.com> (Kevin Hilman's message of "Fri\, 2 Oct 2009 11\:14\:50 -0700")
Kevin Hilman <khilman@deeprootsystems.com> writes:
> These fixes are primarily for PRCM interrupt handler bugs
> and GPIO wakeup support.
>
> Jon Hunter (1):
> OMAP3: PM: Prevent hang in prcm_interrupt_handler
>
> Kevin Hilman (1):
> OMAP3: PM: Enable GPIO module-level wakeups
>
> Paul Walmsley (2):
> OMAP3: PM: PRCM interrupt: check MPUGRPSEL register
> OMAP3: PM: PRCM interrupt: only handle selected PRCM interrupts
>
> Vikram Pandita (1):
> OMAP3: PM: USBHOST: clear wakeup events on both hosts
>
Here's one more for the PM fixes queue from Atrem.
Kevin
next prev parent reply other threads:[~2009-10-05 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 18:14 [PATCH 0/5] OMAP PM fixes for 2.6.32 Kevin Hilman
2009-10-02 18:14 ` [PATCH 1/5] OMAP3: PM: Prevent hang in prcm_interrupt_handler Kevin Hilman
2009-10-02 18:14 ` [PATCH 2/5] OMAP3: PM: PRCM interrupt: check MPUGRPSEL register Kevin Hilman
2009-10-02 18:14 ` [PATCH 3/5] OMAP3: PM: PRCM interrupt: only handle selected PRCM interrupts Kevin Hilman
2009-10-02 18:14 ` [PATCH 4/5] OMAP3: PM: USBHOST: clear wakeup events on both hosts Kevin Hilman
2009-10-02 18:14 ` [PATCH 5/5] OMAP3: PM: Enable GPIO module-level wakeups Kevin Hilman
2009-10-05 17:57 ` Kevin Hilman [this message]
2009-10-05 18:02 ` [PATCH 0/5] OMAP PM fixes for 2.6.32 Kevin Hilman
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=877hv9yb9l.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.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).