From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] power: introduce library for device-specific OPPs
Date: Sat, 18 Sep 2010 00:48:54 -0500 [thread overview]
Message-ID: <4C9452C6.8010308@ti.com> (raw)
In-Reply-To: <4C945139.20602@ti.com>
Menon, Nishanth had written, on 09/18/2010 12:42 AM, the following:
> Greg KH had written, on 09/18/2010 12:38 AM, the following:
>> On Sat, Sep 18, 2010 at 12:24:19AM -0500, Nishanth Menon wrote:
>>> This is hence introduced under lib allowing all architectures to
>>> selectively enable the feature based on their capabilities.
>> <snip>
>>
>>> Documentation/power/00-INDEX | 2 +
>>> Documentation/power/opp.txt | 326 ++++++++++++++++++++++++++
>>> drivers/base/power/Makefile | 1 +
>>> drivers/base/power/opp.c | 527 ++++++++++++++++++++++++++++++++++++++++++
>>> include/linux/opp.h | 126 ++++++++++
>>> kernel/power/Kconfig | 14 ++
>>> 6 files changed, 996 insertions(+), 0 deletions(-)
>>> create mode 100644 Documentation/power/opp.txt
>>> create mode 100644 drivers/base/power/opp.c
>>> create mode 100644 include/linux/opp.h
>> That doesn't look like the files are under lib/
>>
>> Did you forget to move them, or do you need to update the changelog
>> message?
>
> Aww... and I thought I fixed them all.. the commit message is wrong.
> we had an alignment earlier today to move it from lib to
> drivers/base/power [1] :(
>
> Thanks for catching it. Will fix it in rev 3 after collating any further
> comments as well.
>
> [1] http://marc.info/?l=linux-arm-kernel&m=128476405731191&w=2
Yikes..sleepy eyes and long threads don't go well together :(
[1] http://marc.info/?l=linux-arm-kernel&m=128476651001280&w=2 is the
link I had intended
apologies on the spam.. :(
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2010-09-18 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 5:24 [PATCH v2] power: introduce library for device-specific OPPs Nishanth Menon
2010-09-18 5:38 ` Greg KH
2010-09-18 5:42 ` Nishanth Menon
2010-09-18 5:48 ` Nishanth Menon [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=4C9452C6.8010308@ti.com \
--to=nm@ti.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).