* linux-next: manual merge of the kbuild tree with the sparc-next tree
@ 2012-05-16 3:44 Stephen Rothwell
2012-05-16 3:57 ` David Miller
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2012-05-16 3:44 UTC (permalink / raw)
To: Michal Marek; +Cc: linux-next, linux-kernel, Sam Ravnborg, David S. Miller
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Hi Michal,
Today's linux-next merge of the kbuild tree got a conflict in
arch/sparc/boot/Makefile between commit 51f19cfa76d7 ("sparc32: drop
build time btfixup patching") from the sparc-next tree and commit
95698570510b ("kbuild: refactor final link of sparc32") from the kbuild
tree.
I have no idea, so I used the version from the sparc-next tree.
Sam, can you have a look and work this out, please?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the kbuild tree with the sparc-next tree
2012-05-16 3:44 linux-next: manual merge of the kbuild tree with the sparc-next tree Stephen Rothwell
@ 2012-05-16 3:57 ` David Miller
2012-05-16 4:46 ` Sam Ravnborg
0 siblings, 1 reply; 3+ messages in thread
From: David Miller @ 2012-05-16 3:57 UTC (permalink / raw)
To: sfr; +Cc: mmarek, linux-next, linux-kernel, sam
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 16 May 2012 13:44:30 +1000
> Today's linux-next merge of the kbuild tree got a conflict in
> arch/sparc/boot/Makefile between commit 51f19cfa76d7 ("sparc32: drop
> build time btfixup patching") from the sparc-next tree and commit
> 95698570510b ("kbuild: refactor final link of sparc32") from the kbuild
> tree.
>
> I have no idea, so I used the version from the sparc-next tree.
>
> Sam, can you have a look and work this out, please?
As Sam states in:
http://patchwork.ozlabs.org/patch/159094/
This patch will conflict badly with a patch in kbuild-next.
The fix is simple - drop all changes from kbuild-next.
:-)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the kbuild tree with the sparc-next tree
2012-05-16 3:57 ` David Miller
@ 2012-05-16 4:46 ` Sam Ravnborg
0 siblings, 0 replies; 3+ messages in thread
From: Sam Ravnborg @ 2012-05-16 4:46 UTC (permalink / raw)
To: David Miller; +Cc: sfr, mmarek, linux-next, linux-kernel
On Tue, May 15, 2012 at 11:57:47PM -0400, David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 16 May 2012 13:44:30 +1000
>
> > Today's linux-next merge of the kbuild tree got a conflict in
> > arch/sparc/boot/Makefile between commit 51f19cfa76d7 ("sparc32: drop
> > build time btfixup patching") from the sparc-next tree and commit
> > 95698570510b ("kbuild: refactor final link of sparc32") from the kbuild
> > tree.
> >
> > I have no idea, so I used the version from the sparc-next tree.
> >
> > Sam, can you have a look and work this out, please?
>
> As Sam states in:
>
> http://patchwork.ozlabs.org/patch/159094/
>
> This patch will conflict badly with a patch in kbuild-next.
>
> The fix is simple - drop all changes from kbuild-next.
>
> :-)
The above comment is true for both arch/sparc/Makefile and
arch/sparc/bot/Makefile.
sparc-next will also conflict with net-next.
net-next add the following line to arch/sparc/Makefile:
+core-y += arch/sparc/net/
The fix is to add this line to the newly introduced
arch/sparc/Kbuild file like this:
obj-y += net/
Sorry for these conflicts but we have been busy in sparc land
this round.
Sam
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-05-16 4:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-16 3:44 linux-next: manual merge of the kbuild tree with the sparc-next tree Stephen Rothwell
2012-05-16 3:57 ` David Miller
2012-05-16 4:46 ` Sam Ravnborg
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).