lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2100649.OqVGEpXy07@vostro.rjw.lan>
Date:	Mon, 06 Jan 2014 02:32:24 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Viresh Kumar <viresh.kumar@...aro.org>,
	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpufreq: arm-big-little: Make driver dependent on CONFIG_BIG_LITTLE

On Monday, January 06, 2014 01:11:37 AM Russell King - ARM Linux wrote:
> On Mon, Jan 06, 2014 at 02:23:39AM +0100, Rafael J. Wysocki wrote:
> > On Monday, January 06, 2014 12:58:56 AM Russell King - ARM Linux wrote:
> > > 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@....linux.org.uk>
> > > > > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.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.
> > 
> > Well, it can go into 3.13 too.
> > 
> > Thanks!
> 
> Thanks.

Well, actually, I was wrong.  It depends on stuff already queued up for 3.14,
so either I'd need to drag all that into 3.13, or it needs to wait for 3.14.

So it will wait, sorry about that.

Thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ