From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: sboyd@codeaurora.org, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org, nm@ti.com, khilman@linaro.org
Subject: Re: [PATCH V2 Resend 0/5] PM / OPP: Add debugfs support
Date: Thu, 3 Sep 2015 10:02:12 +0530 [thread overview]
Message-ID: <20150903043212.GF13140@linux> (raw)
In-Reply-To: <1528146.dlEkeu6D3U@vostro.rjw.lan>
On 03-09-15, 03:05, Rafael J. Wysocki wrote:
> This series is generally fine by me, but it causes too much code churn
> to happen for pushing it into 4.3 at this point. I can queue it up
> for the next merge widnow.
Thanks for letting me know :)
I wasn't initially trying for 4.3, but 4.4. But sent this again to get
it Acked, so that the path for next series gets clear :)
I am currently working on multiple-regulator support and that will
have lot of updates too.
Thanks.
--
viresh
prev parent reply other threads:[~2015-09-03 4:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 4:58 [PATCH V2 Resend 0/5] PM / OPP: Add debugfs support Viresh Kumar
2015-09-01 4:58 ` [PATCH V2 Resend 1/5] PM / OPP: reuse of_parse_phandle() Viresh Kumar
2015-09-01 22:48 ` Stephen Boyd
2015-09-01 4:58 ` [PATCH V2 Resend 2/5] PM / OPP: Prefix exported opp routines with dev_pm_opp_ Viresh Kumar
2015-09-01 19:03 ` Pavel Machek
2015-09-02 7:22 ` Viresh Kumar
2015-09-02 7:25 ` Viresh Kumar
2015-09-03 0:00 ` Stephen Boyd
2015-09-01 4:58 ` [PATCH V2 Resend 3/5] PM / OPP: Move opp core to its own directory Viresh Kumar
2015-09-01 22:51 ` Stephen Boyd
2015-09-02 7:13 ` Viresh Kumar
2015-09-01 4:58 ` [PATCH V2 Resend 4/5] PM / OPP: Move cpu specific code to opp/cpu.c Viresh Kumar
2015-09-01 4:58 ` [PATCH V2 Resend 5/5] PM / OPP: Add debugfs support Viresh Kumar
2015-09-01 23:00 ` Stephen Boyd
2015-09-03 1:05 ` [PATCH V2 Resend 0/5] " Rafael J. Wysocki
2015-09-03 4:32 ` Viresh Kumar [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=20150903043212.GF13140@linux \
--to=viresh.kumar@linaro.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.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).