From: Geert Uytterhoeven <geert@linux-m68k•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Rusty Russell <rusty@rustcorp•com.au>,
linux-next@vger•kernel.org,
Linux/m68k <linux-m68k@vger•kernel.org>
Subject: Re: linux-next: boot-params tree build failure
Date: Wed, 17 Dec 2008 09:18:32 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0812170915400.29433@anakin> (raw)
In-Reply-To: <20081217165557.b4898a4b.sfr@canb.auug.org.au>
On Wed, 17 Dec 2008, Stephen Rothwell wrote:
> The build of next-20081216 (m68k defconfig) failed like this:
>
> arch/m68k/kernel/setup.c:230: error: conflicting types for '_end'
> arch/m68k/kernel/setup.c:215: error: previous declaration of '_end' was here
>
> Caused by commit 0de5c2d9f02d2018fd671ca1015432dffa5eb338 ("param:
> arch_get_boot_command_line()") from the poot-params tree.
This is due to the existing
extern int _etext, _edata, _end;
in and the newly added
extern char _end[];
to arch/m68k/kernel/setup.c.
As these are already declared in asm-generic/sections.h (which is used by
asm-m68k/sections.h), I'll switch arch/m68k/kernel/setup.c to using them.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-12-17 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 5:55 linux-next: boot-params tree build failure Stephen Rothwell
2008-12-17 8:18 ` Geert Uytterhoeven [this message]
2008-12-21 11:12 ` [PATCH] m68k: Kill several external declarations in source files (was: Re: linux-next: boot-params tree build failure) Geert Uytterhoeven
2008-12-21 22:21 ` Rusty Russell
2008-12-22 7:30 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2008-12-17 6:40 linux-next: boot-params tree build failure Stephen Rothwell
2008-12-17 7:04 ` Stephen Rothwell
2008-12-15 13:20 Stephen Rothwell
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=Pine.LNX.4.64.0812170915400.29433@anakin \
--to=geert@linux-m68k$(echo .)org \
--cc=linux-m68k@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rusty@rustcorp$(echo .)com.au \
--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