linux-kernel - next-200110804 ARM build break (cpuidle_call

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-next>] [day] [month] [year] [list]

Date:	Thu, 4 Aug 2011 13:35:59 -0700
From:	Stephen Warren <swarren@...dia.com>
To:	Len Brown <len.brown@...el.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	"Mark Brown (broonie@...nsource.wolfsonmicro.com)" 
	<broonie@...nsource.wolfsonmicro.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: next-200110804 ARM build break (cpuidle_call_idle)

With next-20110804, I'm seeing the following on ARM:

arch/arm/kernel/process.c: In function 'cpu_idle':
arch/arm/kernel/process.c:200: error: implicit declaration of function 'cpuidle_call_idle'

This was previously fixed with:

https://lkml.org/lkml/2011/4/4/109

Commit 5f8cf82 (cpuidle: stop using pm_idle) converted arches to use
cpuidle_idle_call() but contained typos on ARM and SH transposing the
function name into cpuidle_call_idle().

Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>

(which I think was included directly in linux-next according to that
email thread)

However, commit 5f8cf82 isn't in linux-next any more, but instead,
a0bfa13 "cpuidle: stop depending on pm_idle" has replaced it, and has
the same issue.

Applying Mark's previous fix solves the build problem.

Related, I see that linux-next merges
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git idle-test
yet that branch doesn't seem to exist anymore.

-- 
nvpublic

--
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/