From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Cc: mlan@cpu.lu
Subject: Re: defconfig for pmac in 2.3.51 and up
Date: Sun, 12 Mar 2000 19:46:46 +0100 [thread overview]
Message-ID: <38CBE616.DD8B9D37@wanadoo.fr> (raw)
In-Reply-To: 200003121551.QAA00488@piglet.grunz.lu
Michel Lanners wrote:
> >> (digging a little further...) Oh I see, bitkeeper doesn't have the
> >> complete collection of arch/ppc/configs/*_defconfig files any more; no
> >> more chrp, pmac, or prep. I still have them from a previous version.
> >> Weird...
>
> Wouldn't this be a side-effect of trying to 'unify' all the PPC
> configs? There's only a generic PPC config option as well, an no more
> CONFIG_PMAC, CONFIG_PREP, CONFIG_CHRP etc.., thy are all replaced by
> the single CONFIG_ALL_PPC.
If this disappearance of the 3 defconfig files is by purpose, then the
arch/ppc/Makefile should be told about it, too. There you still find 9
different *_config targets, but 3 of them won't work because the
respective *_defconfig files have disappeared. The 6 other oddball
*_defconfig files are still there.
> I think it still makes sense, though, to keep the default configs for
> each hardware type. Makes kernel config a lot easier...
Developers only ever use make oldconfig, so the other make *config
options are notoriously untested.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-03-12 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-12 9:34 defconfig for pmac in 2.3.51 and up andreas tobler
2000-03-12 12:37 ` Martin Costabel
2000-03-12 13:00 ` Andreas Tobler
2000-03-12 15:51 ` Michel Lanners
2000-03-12 18:46 ` Martin Costabel [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=38CBE616.DD8B9D37@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).