From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] OMAP: misc. PM-related fixes for v3.1-rc
Date: Wed, 10 Aug 2011 03:39:44 -0700 [thread overview]
Message-ID: <20110810103944.GF1939@atomide.com> (raw)
In-Reply-To: <20110809111443.GQ1866@atomide.com>
* Tony Lindgren <tony@atomide.com> [110809 04:09]:
> * Kevin Hilman <khilman@ti.com> [110804 08:38]:
> > Hi Tony,
> >
> > Here's my current collection of PM-related fixes for the -rc cycle.
> >
> > They are based on the next/board branch of Arnd's arm-soc tree (which
> > has already been merged by Linus) and are also available in the
> > for_3.1/pm-fixes branch of my tree:
> > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
>
> Thanks, based on your comment looks like you want to modify at least
> one of them. I'll pick the ones that should get merged immediately
> while you're on vacation.
Hmm as it looks like you already dropped the last patch, I'll pull
the first five into fixes.
Tony
prev parent reply other threads:[~2011-08-10 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 15:45 [PATCH 0/6] OMAP: misc. PM-related fixes for v3.1-rc Kevin Hilman
2011-08-04 15:45 ` [PATCH 1/6] OMAP2+: Kconfig: don't select PM in OMAP2PLUS_TYPICAL Kevin Hilman
2011-08-04 15:45 ` [PATCH 2/6] OMAP3+: SR: ensure pm-runtime callbacks can be invoked with IRQs disabled Kevin Hilman
2011-08-04 15:45 ` [PATCH 3/6] OMAP1: enable GENERIC_IRQ_CHIP Kevin Hilman
2011-08-04 15:45 ` [PATCH 4/6] OMAP3: beagle: don't touch omap_device internals Kevin Hilman
2011-08-04 15:45 ` [PATCH 5/6] OMAP2+: PM: SmartReflex: use put_sync_suspend for IRQ-safe disabling Kevin Hilman
2011-08-04 15:45 ` [PATCH 6/6] OMAP: McBSP: use existing macros for converting between devices Kevin Hilman
2011-08-05 6:02 ` Jarkko Nikula
2011-08-05 14:57 ` Kevin Hilman
2011-08-09 11:14 ` [PATCH 0/6] OMAP: misc. PM-related fixes for v3.1-rc Tony Lindgren
2011-08-10 10:39 ` 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=20110810103944.GF1939@atomide.com \
--to=tony@atomide.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).