All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: Len Brown <len.brown@intel.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Mark Brown (broonie@opensource.wolfsonmicro.com)" 
	<broonie@opensource.wolfsonmicro.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: next-200110804 ARM build break (cpuidle_call_idle)
Date: Thu, 4 Aug 2011 13:35:59 -0700	[thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF049EEAB704@HQMAIL01.nvidia.com> (raw)

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@opensource.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


             reply	other threads:[~2011-08-04 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 20:35 Stephen Warren [this message]
2011-08-04 23:04 ` next-200110804 ARM build break (cpuidle_call_idle) Stephen Rothwell
2011-08-04 23:29 ` Stephen Rothwell
2011-08-05  0:52   ` Stephen Rothwell
2011-08-05  2:42     ` Linus Torvalds
2011-08-05  8:21       ` Ingo Molnar
2011-08-05 19:44       ` Brown, Len

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=74CDBE0F657A3D45AFBB94109FB122FF049EEAB704@HQMAIL01.nvidia.com \
    --to=swarren@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.