From: Denis Vlasenko <vda.linux@googlemail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Jiri Kosina <jikos@jikos.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: whence CONFIG_PROVE_SPIN_LOCKING?
Date: Sun, 18 Mar 2007 22:42:21 +0100 [thread overview]
Message-ID: <200703182242.21221.vda.linux@googlemail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703181655430.28474@CPE00045a9c397f-CM001225dbafb6>
Hi,
On Sunday 18 March 2007 22:06, Robert P. J. Day wrote:
> p.s. just FYI, i ran my "find dead CONFIG variables" script on the
> entire tree and, as we speak, there are 316 preprocessor tests that
> are testing variables of the form "CONFIG_whatever" for which that
> option is not set anywhere in the tree. (that is, 316 distinct
> variables, not just 316 distinct tests.) see the attached script and
> feel free to run it from the top of the tree on your favourite
> directory or sub-directory.
In busybox project we adopted the usage of -Wundef
and we try to minimize usage of #ifdef CONFIG_xxx - each boolean
CONFIG_xxx option for busybox is accompanied with
ENABLE_xxx #define which is 1 or 0, never "undefined",
and we check it instead of CONFIG_xxx.
Because if -Wundef, gcc complains whenever we use #if
on undefined ENABLE_xxx.
--
vda
prev parent reply other threads:[~2007-03-18 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 20:26 whence CONFIG_PROVE_SPIN_LOCKING? Robert P. J. Day
2007-03-18 20:57 ` Jiri Kosina
2007-03-18 21:06 ` Robert P. J. Day
2007-03-18 21:42 ` Denis Vlasenko [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=200703182242.21221.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rpjday@mindspring.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.