mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: mismatch between default and defconfig LOG_BUF_SHIFT values
Date: Tue, 28 Nov 2006 05:02:41 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0611280451010.13481@localhost.localdomain> (raw)


  not like it's a big deal, but there's a minor incongruity between
the default values for LOG_BUF_SHIFT for IA64 depending on whether
you're configuring for the first time or not.

  if i'm configuring with a fresh tree for the first time (so that
there's no .config file) and i run:

  $ make ARCH=ia64 menuconfig    (on my x86 system, just for fun)

then the initial value for LOG_BUF_SHIFT is obtained from
arch/ia64/defconfig:

  CONFIG_LOG_BUF_SHIFT=20

however, once i do that initial config, if i deselect "Kernel
debugging" and later reselect it, the new default value of 16 for that
config option comes from lib/Kconfig.debug:

...
config LOG_BUF_SHIFT
        int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
        range 12 21
        default 17 if S390 || LOCKDEP
        default 16 if X86_NUMAQ || IA64     <-- 16, not 20
...

  is it worth trying to bring the Kconfig.debug default values into
line with the defconfig file values, to avoid any possible confusion?

rday




             reply	other threads:[~2006-11-28 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 10:02 Robert P. J. Day [this message]
2006-11-28 10:15 ` Arjan van de Ven
2006-11-28 10:55   ` Robert P. J. Day

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.0611280451010.13481@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linux-kernel@vger.kernel.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®