From: behanw@websterwood•com (Behan Webster)
To: linux-arm-kernel@lists•infradead.org
Subject: vexpress compilation error in next-20121127
Date: Fri, 14 Dec 2012 09:47:17 -0500 [thread overview]
Message-ID: <50CB3BF5.4000202@websterwood.com> (raw)
In-Reply-To: <1355478545.26914.2.camel@hornet>
On 12/14/12 04:49, Pawel Moll wrote:
> On Thu, 2012-12-13 at 19:07 +0000, Behan Webster wrote:
>> On 11/27/12 20:16, Markus Mayer wrote:
>>> Hi Pawel,
>>>
>>> There seems to be an issue compiling vexpress at this point. The
>>> problem being that vexpress' makefile references reset.o, but there's
>>> no reset.c in arch/arm/mach-vexpress.
>>>
>>> [...]
>>> CC arch/arm/mach-bcm/board_bcm.o
>>> LD arch/arm/mach-bcm/built-in.o
>>> CC arch/arm/mach-vexpress/v2m.o
>>> make[1]: *** No rule to make target `arch/arm/mach-vexpress/reset.o',
>>> needed by `arch/arm/mach-vexpress/built-in.o'. Stop.
>>> make: *** [arch/arm/mach-vexpress] Error 2
>> Same issue in mainline now too: arch/arm/mach-vexpress/reset.c is missing.
> Yes, I've noticed this myself. It's just that the pull request for the
> arm-soc drivers branch went out in the second batch yesterday
> (http://article.gmane.org/gmane.linux.kernel/1409413), while the soc one
> in the first one.
I see it now. Thanks!
> This was a bad decision to split the reset driver from
> the main update series, apologies about this.
No worries. Just making sure the issue didn't go unnoticed.
Thanks again,
Behan
--
Behan Webster
behanw at websterwood.com
prev parent reply other threads:[~2012-12-14 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 1:16 vexpress compilation error in next-20121127 Markus Mayer
2012-11-28 12:36 ` Pawel Moll
2012-11-28 20:53 ` Markus Mayer
2012-11-29 11:39 ` Pawel Moll
2012-11-29 20:03 ` Markus Mayer
2012-12-13 19:07 ` Behan Webster
2012-12-14 9:49 ` Pawel Moll
2012-12-14 14:47 ` Behan Webster [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=50CB3BF5.4000202@websterwood.com \
--to=behanw@websterwood$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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