From: Lucas Stach <l.stach@pengutronix.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Mark Brown <broonie@kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH resend] cpufreq: dt: disable unsupported OPPs
Date: Thu, 02 Oct 2014 13:57:55 +0200 [thread overview]
Message-ID: <1412251075.4875.3.camel@pengutronix.de> (raw)
In-Reply-To: <CAKohpon9buGWmcXH9+PmtatmbnOro+gU84zkskPjNZ6fiM5SLQ@mail.gmail.com>
Am Donnerstag, den 02.10.2014, 10:54 +0530 schrieb Viresh Kumar:
> On 2 October 2014 02:09, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > Would you mind sending it again with the fix folded in for me?
>
> Done.
I don't know how it makes sense to fold the fix into this patch. It has
nothing to do with the rename.
If you want to fold the fix in the relevant patch this would be
"cpufreq: cpu0: Move per-cluster initialization code to ->init()"
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-10-02 11:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 15:29 [PATCH resend] cpufreq: dt: disable unsupported OPPs Lucas Stach
2014-09-30 19:53 ` Rafael J. Wysocki
2014-10-01 3:29 ` Viresh Kumar
2014-10-01 20:39 ` Rafael J. Wysocki
2014-10-02 5:24 ` Viresh Kumar
2014-10-02 11:57 ` Lucas Stach [this message]
2014-10-02 17:33 ` Rafael J. Wysocki
2014-10-08 22:36 ` Rafael J. Wysocki
2014-10-09 3:43 ` Viresh Kumar
2014-10-12 20:27 ` Rafael J. Wysocki
2014-10-16 10:08 ` [RESEND 2] " Lucas Stach
2014-10-21 14:19 ` Rafael J. Wysocki
2014-10-23 9:19 ` Geert Uytterhoeven
2014-10-23 14:10 ` Lucas Stach
2014-10-23 14:43 ` Geert Uytterhoeven
2014-10-23 15:13 ` Lucas Stach
2014-10-23 21:26 ` Rafael J. Wysocki
2014-10-24 0:26 ` Khiem Nguyen
2014-10-24 10:19 ` Lucas Stach
2014-10-24 12:30 ` Geert Uytterhoeven
2014-10-24 12:39 ` Lucas Stach
2014-10-24 13:01 ` 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=1412251075.4875.3.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=broonie@kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).