public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: <mingo@elte.hu>, "Harvey Harrison" <harvey.harrison@gmail.com>,
	<tglx@linutronix.de>, "Roman Zippel" <zippel@linux-m68k.org>,
	"Nick Piggin" <npiggin@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: def_bool n
Date: Mon, 04 Aug 2008 13:29:06 +0100	[thread overview]
Message-ID: <48971232.76E4.0078.0@novell.com> (raw)

Could either of you clarify what the significance of such a construct
(encountered several times in arch/x86/Kconfig alone) is?

At first, I noticed it only with GENERIC_LOCKBREAK (it is my
understanding that this block can go away entirely), but then realized
that with the bool->def_bool conversion this was introduced in various
other places (where "default n" was used before, which seems as
pointless a statement). Am I missing something?

Thanks, Jan



             reply	other threads:[~2008-08-04 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 12:29 Jan Beulich [this message]
2008-08-04 21:16 ` def_bool n Sam Ravnborg

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=48971232.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=tglx@linutronix.de \
    --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