* linux-next: microblaze tree build failure
@ 2009-11-19 22:56 Stephen Rothwell
2009-11-20 16:31 ` Nathan Fontenot
2009-11-20 20:23 ` Grant Likely
0 siblings, 2 replies; 3+ messages in thread
From: Stephen Rothwell @ 2009-11-19 22:56 UTC (permalink / raw)
To: Michal Simek; +Cc: linux-next, linux-kernel, Nathan Fontenot
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: microblaze tree build failure
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
1 sibling, 0 replies; 3+ messages in thread
From: Nathan Fontenot @ 2009-11-20 16:31 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Michal Simek, linux-next, linux-kernel
Yes, this should be rejected. I have submitted an updated patch to
linuxppc-dev and devicetree-discuss.
I'm not sure how this patch git picked up, I didn't think it did.
Looking at the coimmit it appears that only patch 1/4 of the patchset
was picked up.
-Nathan Fontenot
Stephen Rothwell 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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: microblaze tree build failure
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
1 sibling, 0 replies; 3+ messages in thread
From: Grant Likely @ 2009-11-20 20:23 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Michal Simek, linux-next, linux-kernel, Nathan Fontenot
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-11-20 20:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).