From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: [ANNOUNCE] updated PM branch, 2.6.32-rc5 + l-o master
Date: Fri, 23 Oct 2009 10:18:46 -0700 [thread overview]
Message-ID: <877humghah.fsf@deeprootsystems.com> (raw)
Hello,
I've rebased/updated the PM branch based on current linux-omap master
branch (2.6.32-rc1 based.)
The only changes this time were related to the #include path changes
and the IO_ADDRESS changes. There were no (intentional) functional
changes.
I've also updated the OMAP Power Management wiki[1], and the 'Current
version' section highlights the changes and supported platforms.
I've also updated the 'mainline plans' section to reflect what is
already in mailine, what is being submitted for the coming merge
window and what is still left in the PM branch.
Kevin
[1] http://elinux.org/OMAP_Power_Management
reply other threads:[~2009-10-23 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877humghah.fsf@deeprootsystems.com \
--to=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