linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [patch 00/13] CPU selection Kconfig cleanup, take 3
Date: Sun, 17 Jun 2007 02:22:22 +0200	[thread overview]
Message-ID: <f8a87cbd246847e830d0e6e986eec408@kernel.crashing.org> (raw)
In-Reply-To: <200706170214.11247.arnd@arndb.de>

>> People have run into the issue so I think it desires at least a =A0
>> little concern. =A0See: http://marc.info/?t=3D117529164800005&r=3D1&w=3D=
2
>
> But isn't the reported problem just a bug in the build system?

Yes, that's a completely separate bug.

> My impression was that the user did not complain about the fact
> that the kernel he was trying to build would not boot on any
> platform, but rather that the kernel tried to build a zImage
> that was not defined, resulting in a build error.

It's the only valid complaint, anyway :-)

> Obviously, any configuration that can be selected by the user
> should be able to compile and link without errors, even if it's
> not particularly useful.

Yes.


Segher

  reply	other threads:[~2007-06-17  0:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 16:30 [patch 00/13] CPU selection Kconfig cleanup, take 3 arnd
2007-06-12 16:30 ` [patch 01/13] powerpc: split out CPU specific options into a new Kconfig file arnd
2007-06-12 16:30 ` [patch 02/13] powerpc: move 82xx/83xx/86xx Kconfig options to platform selection arnd
2007-06-12 16:30 ` [patch 03/13] powerpc: rename add_bridge to avoid namespace clashes arnd
2007-06-12 16:30 ` [patch 04/13] powerpc: multiplatformize 8{2,3,6}xx configuration arnd
2007-06-12 16:30 ` [patch 05/13] powerpc: multiplatformize embedded6xx configuration arnd
2007-06-12 16:30 ` [patch 06/13] powerpc: multiplatformize 52xx configuration arnd
2007-06-12 16:30 ` [patch 07/13] powerpc: multiplatformize 85xx configuration arnd
2007-06-12 16:30 ` [patch 08/13] powerpc: autoselect PPC_MULTIPLATFORM arnd
2007-06-12 16:30 ` [patch 09/13] powerpc: autoselect optimal -mcpu= flag by platform arnd
2007-06-12 16:30 ` [patch 10/13] powerpc: mpc82xx_ads build fix arnd
2007-06-12 16:30 ` [patch 11/13] powerpc: killl isa_{io,mem}_base definitions for !PCI arnd
2007-06-12 16:30 ` [patch 12/13] powerpc: fix building without PCI arnd
2007-06-14  1:44   ` Paul Mackerras
2007-06-14  7:58     ` Arnd Bergmann
2007-06-12 16:30 ` [patch 13/13] disallow building powermac and tsi108 " arnd
2007-06-14  1:46 ` [patch 00/13] CPU selection Kconfig cleanup, take 3 Paul Mackerras
2007-06-14 13:33   ` Kumar Gala
2007-06-14 23:51     ` Arnd Bergmann
2007-06-16 23:52       ` Kumar Gala
2007-06-17  0:14         ` Arnd Bergmann
2007-06-17  0:22           ` Segher Boessenkool [this message]
2007-06-17 14:46           ` Kumar Gala
2007-06-17 23:09             ` Arnd Bergmann
2007-06-18  4:32               ` Kumar Gala
2007-06-19  0:05                 ` Kumar Gala
2007-06-15 18:28     ` Kim Phillips
2007-06-16 23:48       ` Kumar Gala
2007-06-16  0:46     ` Benjamin Herrenschmidt
2007-06-16 23:47       ` Kumar Gala
2007-06-17  0:19         ` Segher Boessenkool

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=f8a87cbd246847e830d0e6e986eec408@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).