From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: mvebu: build error in -next
Date: Wed, 11 Jun 2014 14:07:40 +0200 [thread overview]
Message-ID: <20140611140740.1bbe4a94@free-electrons.com> (raw)
In-Reply-To: <20140609185550.GA5034@arch.cereza>
Dear Ezequiel Garcia,
On Mon, 9 Jun 2014 15:55:50 -0300, Ezequiel Garcia wrote:
> It seems we have a build error in latest -next (20140606):
>
> arch/arm/mach-mvebu/built-in.o: In function `armada_370_xp_cpu_resume':
> /home/zeta/fast/linux/next/arch/arm/mach-mvebu/pmsu.c:145: undefined reference to `cpu_resume'
> arch/arm/mach-mvebu/built-in.o: In function `armada_370_xp_cpu_suspend':
> /home/zeta/fast/linux/next/arch/arm/mach-mvebu/pmsu.c:223: undefined reference to `cpu_suspend'
>
> Find the config is enclosed; it's probably just a few ifdef's to add.
Thanks for reporting this, I've just sent a patch to fix it.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-11 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 18:55 mvebu: build error in -next Ezequiel Garcia
2014-06-11 12:07 ` Thomas Petazzoni [this message]
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=20140611140740.1bbe4a94@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox