From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: arm-big-little: Make driver dependent on CONFIG_BIG_LITTLE
Date: Mon, 6 Jan 2014 00:58:56 +0000 [thread overview]
Message-ID: <20140106005856.GD27432@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <39696841.2xGCnmPGdl@vostro.rjw.lan>
On Mon, Jan 06, 2014 at 02:08:21AM +0100, Rafael J. Wysocki wrote:
> On Friday, January 03, 2014 03:51:39 PM Viresh Kumar wrote:
> > arm_big_little cpufreq driver is only used for ARM bigLITTLE platforms and hence
> > must be dependent on CONFIG_BIG_LITTLE.
> >
> > This was highlighted by Russell earlier when he reported this issue:
> >
> > drivers/built-in.o: In function `bL_cpufreq_set_rate':
> > powercap_sys.c:(.text+0x5ed9a0): undefined reference to `bL_switch_request_cb'
> >
> > Reported-by: Russell King <linux@arm.linux.org.uk>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Queued up for 3.14, thanks!
This is actually a build fix, not a new feature, so IMHO it should go
in for 3.13. Linus has said he's going to do -rc8 anyway next weekend
so -final is at the earliest two weeks away.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-06 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 10:21 [PATCH] cpufreq: arm-big-little: Make driver dependent on CONFIG_BIG_LITTLE Viresh Kumar
2014-01-06 1:08 ` Rafael J. Wysocki
2014-01-06 0:58 ` Russell King - ARM Linux [this message]
2014-01-06 1:23 ` Rafael J. Wysocki
2014-01-06 1:11 ` Russell King - ARM Linux
2014-01-06 1:32 ` 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=20140106005856.GD27432@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.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