From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
nm@ti.com
Subject: Re: [PATCH V2 0/4] OPP: Some cleanups
Date: Wed, 28 Oct 2015 11:48:54 -0700 [thread overview]
Message-ID: <20151028184854.GY19782@codeaurora.org> (raw)
In-Reply-To: <20151028084007.GH30039@ubuntu>
On 10/28, Viresh Kumar wrote:
> On 28-10-15, 09:25, Rafael J. Wysocki wrote:
> > On Thursday, October 15, 2015 09:42:42 PM Viresh Kumar wrote:
> > > Rafael,
> > >
> > > These are some random cleanups, which were part of the multi-regulator
> > > series earlier. Sending them separately to make that series a bit light
> > > weight.
> > >
> > > V1->V2:
> > > - Just sending them separately.
> > >
> > > Viresh Kumar (4):
> > > PM / OPP: Improve debug print messages with pr_fmt
> > > PM / OPP: Rename routines specific to old bindings with _v1
> > > PM / OPP: Parse all power-supply related bindings together
> > > PM / OPP: Create separate structure for regulator/supplies
> > >
> > > drivers/base/power/opp/core.c | 78 +++++++++++++++++++++++++++----------------
> > > drivers/base/power/opp/cpu.c | 3 ++
> > > drivers/base/power/opp/opp.h | 29 +++++++++++-----
> > > 3 files changed, 73 insertions(+), 37 deletions(-)
> >
> > I'd like to receive an ACK from someone like Stephen on this one.
>
> He isn't around probably, I couldn't find him on IRC for last few
> days. I have just asked you (in another reply) to drop the fourth
> patch for now.
>
> Apart from that things are really trivial, renaming/moving code
> around. Please see if those can be included without waiting for
> Stephen to return.
>
Sorry it seems I got booted from freenode and didn't notice. I've
sent Reviewed-by for the three patches.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-10-28 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 16:12 [PATCH V2 0/4] OPP: Some cleanups Viresh Kumar
2015-10-15 16:12 ` [PATCH V2 1/4] PM / OPP: Improve debug print messages with pr_fmt Viresh Kumar
2015-10-15 19:04 ` Stephen Boyd
2015-10-16 5:37 ` Viresh Kumar
2015-10-16 19:20 ` Stephen Boyd
2015-10-17 4:15 ` [PATCH V3 1/4] PM / OPP: Improve " Viresh Kumar
2015-10-28 18:49 ` Stephen Boyd
2015-10-15 16:12 ` [PATCH V2 2/4] PM / OPP: Rename routines specific to old bindings with _v1 Viresh Kumar
2015-10-28 18:48 ` Stephen Boyd
2015-10-15 16:12 ` [PATCH V2 3/4] PM / OPP: Parse all power-supply related bindings together Viresh Kumar
2015-10-28 18:48 ` Stephen Boyd
2015-10-15 16:12 ` [PATCH V2 4/4] PM / OPP: Create separate structure for regulator/supplies Viresh Kumar
2015-10-28 8:37 ` Viresh Kumar
2015-10-28 8:25 ` [PATCH V2 0/4] OPP: Some cleanups Rafael J. Wysocki
2015-10-28 8:40 ` Viresh Kumar
2015-10-28 18:48 ` Stephen Boyd [this message]
2015-11-05 22:44 ` Rafael J. Wysocki
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=20151028184854.GY19782@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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).