All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: kirkwood build failure on mainline
Date: Fri, 01 Apr 2011 23:27:55 +0200	[thread overview]
Message-ID: <87r59lr7ac.fsf@lebrac.rtp-net.org> (raw)

Hi,

Thanks to kautobuild, I've noticed that -rc1 is not building on kirkwood
with following error [1]:

arch/arm/kernel/built-in.o: In function `cpu_suspend':
io.c:(.text+0x4544): undefined reference to `cpu_feroceon_do_suspend'
io.c:(.text+0x4554): undefined reference to `cpu_feroceon_suspend_size'
arch/arm/kernel/built-in.o: In function `cpu_resume':
io.c:(.data+0x1e8): undefined reference to `cpu_feroceon_do_resume'

After looking at other build logs, there are other platform failing with
similar error. I guess it's failing since commit
f6b0fa02e8b0708d17d631afce456524eadf87ff "ARM: pm: add generic CPU
suspend/resume support". In fact, I would say that this commit only
shows that there's a problem and is not really the cause.
A naive explanation would be that ARCH_SUSPEND_POSSIBLE is selected for
theses systems even if suspend is not supported. Adding a "depends on
!CPU_FEROCEON" is making the kernel build.

Would a patch disabling ARCH_SUSPEND_POSSIBLE for all cpu failing to
build with similar error be accepted/welcome or it's just a really
stupid idea ? In case of it being a stupid idea, what would be the right
approach to fix that given that implementing suspend for all failing SoC
is excluded ?

Thanks,
Arnaud

[1]
http://armlinux.simtec.co.uk/kautobuild/2.6.39-rc1-git2/kirkwood_defconfig/zimage.log
[2] for instance:
http://armlinux.simtec.co.uk/kautobuild/2.6.39-rc1-git2/pxa910_defconfig/zimage.log

             reply	other threads:[~2011-04-01 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 21:27 Arnaud Patard (Rtp) [this message]
2011-04-02  8:54 ` kirkwood build failure on mainline Russell King - ARM Linux

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=87r59lr7ac.fsf@lebrac.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.