From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: Build failure with 3.9.3 (Regression 3.9.2->3.9.3)
Date: Mon, 20 May 2013 17:14:11 +0200 [thread overview]
Message-ID: <20130520151411.GD27420@os.inf.tu-dresden.de> (raw)
Hi,
3.9.3 introduced the following build failure:
CC arch/powerpc/kernel/rtas.o
arch/powerpc/kernel/rtas.c: In function =E2=80=98rtas_cpu_state_change_mask=
=E2=80=99:
arch/powerpc/kernel/rtas.c:843:4: error: implicit declaration of function =
=E2=80=98cpu_down=E2=80=99 [-Werror=3Dimplicit-function-declaration]
cc1: all warnings being treated as errors
make[1]: *** [arch/powerpc/kernel/rtas.o] Error 1
make: *** [arch/powerpc/kernel] Error 2
My kernel config has CONFIG_HOTPLUG_CPU off, that's why cpu_down is not
defined. Shall CONFIG_HOTPLUG_CPU just be enabled or should the code in
rtas.c be adapted?
Thanks,
Adam
--=20
Adam adam@os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
next reply other threads:[~2013-05-20 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 15:14 Adam Lackorzynski [this message]
2013-05-21 19:32 ` Build failure with 3.9.3 (Regression 3.9.2->3.9.3) Srivatsa S. Bhat
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=20130520151411.GD27420@os.inf.tu-dresden.de \
--to=adam@os.inf.tu-dresden.de \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).