From: Grant Likely <grant.likely@secretlab•ca>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Michal Simek <michal.simek@petalogix•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Nathan Fontenot <nfont@austin•ibm.com>
Subject: Re: linux-next: microblaze tree build failure
Date: Fri, 20 Nov 2009 13:23:39 -0700 [thread overview]
Message-ID: <fa686aa40911201223t1d82f43an3f52fa2599088d3b@mail.gmail.com> (raw)
In-Reply-To: <20091120095622.5fefb9fa.sfr@canb.auug.org.au>
On Thu, Nov 19, 2009 at 3:56 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Michal,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> arch/powerpc/platforms/built-in.o: In function `.ofdt_write':
> reconfig.c:(.text+0xca08): undefined reference to `.of_attach_node'
> arch/powerpc/platforms/built-in.o: In function `.do_device_node':
> vio.c:(.text+0x1be2c): undefined reference to `.of_attach_node'
>
> Caused by commit 5d0c1c076548e1f8d590a2f70f281b4eb7b3aeb2 ("Merge
> of_attach_node") which I have reverted for today. That patch is missing
> an update to drivers/of/Makefile at least ... and probably some other
> stuff as well.
... and the OF changes shouldn't be going through the microblaze tree.
This looks like it was an accident. Michal?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-11-20 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 22:56 linux-next: microblaze tree build failure Stephen Rothwell
2009-11-20 16:31 ` Nathan Fontenot
2009-11-20 20:23 ` Grant Likely [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=fa686aa40911201223t1d82f43an3f52fa2599088d3b@mail.gmail.com \
--to=grant.likely@secretlab$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=michal.simek@petalogix$(echo .)com \
--cc=nfont@austin$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/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