From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP: device PM constraints: preparatory support
Date: Thu, 22 Dec 2011 10:13:13 -0800 [thread overview]
Message-ID: <20111222181313.GL24444@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112201251010.12660@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [111220 11:21]:
> Hi Tony
>
> These patches prepare for the introduction of the powerdomain device PM
> constraints, via the standard Linux device PM mechanism that Rafael
> Wysocki introduced.
>
> After the powerdomain device PM constraints go in, we should be able to
> remove some of the OMAP PM interface (currently via platform_data function
> pointers) currently in our tree.
Thanks pulling these into hwmod-part2, no idea if we can still get
these in as it's so close to the merge window.
Regards,
Tony
prev parent reply other threads:[~2011-12-22 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 19:53 [GIT PULL] ARM: OMAP: device PM constraints: preparatory support Paul Walmsley
2011-12-22 18:13 ` 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=20111222181313.GL24444@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 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).