From: khilman@kernel•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: defconfigs: use CONFIG_CPUFREQ_DT
Date: Mon, 15 Dec 2014 10:50:37 -0800 [thread overview]
Message-ID: <7h1to0iw76.fsf@deeprootsystems.com> (raw)
In-Reply-To: <2757282.fj6z18fAYb@vostro.rjw.lan> (Rafael J. Wysocki's message of "Mon, 15 Dec 2014 16:00:12 +0100")
"Rafael J. Wysocki" <rjw@rjwysocki•net> writes:
> On Monday, December 15, 2014 09:48:19 AM Viresh Kumar wrote:
>> CONFIG_GENERIC_CPUFREQ_CPU0 disappeared with commit bbcf071969b20f
>> ("cpufreq: cpu0: rename driver and internals to 'cpufreq_dt'") and some
>> defconfigs are still using it instead of the new one.
>>
>> Use the renamed CONFIG_CPUFREQ_DT generic driver.
>>
>> Cc: <stable@vger•kernel.org> # 3.18
>> Reported-by: Nishanth Menon <nm@ti•com>
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro•org>
>
> OK, so who should be applying this?
>
Normally, we take these defconfig changes through the arm-soc tree, and
I think that should continue, otherwise we'll be bound to have conflicts.
Note all the pull requests for this merge window are already sent, but
I'll queue this up in arm-soc/fixes so it can make it during the
v3.19-rc cycle.
Thanks,
Kevin
next prev parent reply other threads:[~2014-12-15 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 4:18 [PATCH] ARM: defconfigs: use CONFIG_CPUFREQ_DT Viresh Kumar
2014-12-15 15:00 ` Rafael J. Wysocki
2014-12-15 14:42 ` Viresh Kumar
2014-12-15 18:50 ` Kevin Hilman [this message]
2014-12-17 16:01 ` Nishanth Menon
2014-12-17 16:28 ` Viresh Kumar
2014-12-17 18:28 ` Kevin Hilman
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=7h1to0iw76.fsf@deeprootsystems.com \
--to=khilman@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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