mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl-lkml@dif.dk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	LKML <linux-kernel@vger.kernel.org>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: Shouldn't kconfig defaults match recommendations in help text?
Date: Tue, 24 Aug 2004 23:14:25 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0408242302540.2770@dragon.hygekrogen.localhost> (raw)
In-Reply-To: <20040824204611.GB26136@mars.ravnborg.org>

On Tue, 24 Aug 2004, Sam Ravnborg wrote:

> On Tue, Aug 24, 2004 at 09:33:09PM +0200, Jesper Juhl wrote:
> > 
> > Which brings me to another thing regarding configs and defaults - there 
> > does not seem to be much relation between the defaults in the various 
> > Kconfig files and the settings in arch/<foo>/defconfig which puzzles me, 
> > especially since "make defconfig" seems to use the stuff from 
> > arch/<foo>/defconfig and not what's specified in Kconfig...
> > Wouldn't it make sense to update the defconfig's to match the Kconfig's 
> > when I make these changes?
> 
> defconfig is only subject for changes by arch-maintainers.
> And defaults provided in Kconfig is mainly valid for i386 anyway -
> so are the Kconfig help text.
> 
Ok, thank you for enlightening me on that. So defaults are chosen first 
from defconfig, and then from Kconfig for options not present in 
defconfig.

I guess I should limit myself to i386 for this or maybe just abandon it 
alltogether. 
It still seems like a good idea though to make the defaults (at least on 
i386) match the help text recommendations, but if defconfig is used over 
Kconfig and defconfig is more or less off-limits, and changing Kconfig 
would result in wrong defaults on other archs (which would then cause more 
work for arch maintainers with updating their defconfig), then maybe it's 
really not such a good idea after all to go about changing this.

I'll stay away from making these changes for now unless I run across some 
really obvious and non-problematic cases.

--
Jesper Juhl


  reply	other threads:[~2004-08-24 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 21:50 Jesper Juhl
2004-08-24 15:01 ` Mikael Pettersson
2004-08-24 17:03   ` Jesper Juhl
2004-08-24 18:29     ` Sam Ravnborg
2004-08-24 19:33       ` Jesper Juhl
2004-08-24 20:46         ` Sam Ravnborg
2004-08-24 21:14           ` Jesper Juhl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23 18:57 Jesper Juhl
2004-08-24 18:52 ` Roman Zippel
2004-08-24 19:36   ` Jesper Juhl

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.61.0408242302540.2770@dragon.hygekrogen.localhost \
    --to=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /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

all inboxes | Powered by JetHome®