From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Linux PM <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] PM / OPP: Move the OPP directory out of power/
Date: Wed, 27 Sep 2017 10:27:05 -0700 [thread overview]
Message-ID: <20170927172705.GA12211@ubuntu> (raw)
In-Reply-To: <CAJZ5v0hcg5bYfhUR2cLZo5bB8gL8F3UeD9Wrbp8TLLQU_agx-A@mail.gmail.com>
On 27-09-17, 19:22, Rafael J. Wysocki wrote:
> On Wed, Sep 27, 2017 at 12:12 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > The drivers/base/power/ directory is special and contains code related
> > to power management core like system suspend/resume, hibernation, etc.
> > It was fine to keep the OPP code inside it when we had just one file for
> > it, but it is growing now and already has a directory for itself.
> >
> > Lets move it directly under drivers/ directory, just like cpufreq and
> > cpuidle.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > V1->V2:
> > - Update maintainers and add a Kconfig file in drivers/opp/.
>
> OK, but I need an ACK from Stephen here.
Sure.
> And while we are at it, you, Stephen and Nishanth Menon are listed as
> maintainers for it and I'm not, but I still apply OPP patches, so
> maybe one of you can set up a git repo for this and send pull requests
> to me instead?
Yeah, I will setup one.
--
viresh
next prev parent reply other threads:[~2017-09-27 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 22:12 [PATCH V2] PM / OPP: Move the OPP directory out of power/ Viresh Kumar
2017-09-27 17:22 ` Rafael J. Wysocki
2017-09-27 17:27 ` Viresh Kumar [this message]
2017-09-27 17:49 ` Rafael J. Wysocki
2017-09-28 4:23 ` Viresh Kumar
2017-09-27 22:15 ` Stephen Boyd
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=20170927172705.GA12211@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=vincent.guittot@linaro.org \
--cc=vireshk@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;
as well as URLs for NNTP newsgroup(s).