From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: marcel@holtmann.org
Subject: dead CONFIG variables: net/bluetooth/
Date: Wed, 2 May 2007 15:51:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705021548050.16336@localhost.localdomain> (raw)
this example is somewhat misleading as some of the bluetooth source
(unfortunately) uses variables that start with the "CONFIG_" prefix
that have nothing to do with the Kconfig files. for clarity, this is
the sort of thing that should be avoided.
obviously, what's happening here is nothing but a bunch of explicit
debugging variables, but it would still be better if they were renamed
to not have that "CONFIG_" prefix (unless, of course, debugging
entries for them are added to the appropriate Kconfig files).
$ ../dead_config.sh net/bluetooth
========== BT_BNEP_DEBUG ==========
net/bluetooth/bnep/netdev.c:#ifndef CONFIG_BT_BNEP_DEBUG
net/bluetooth/bnep/sock.c:#ifndef CONFIG_BT_BNEP_DEBUG
net/bluetooth/bnep/core.c:#ifndef CONFIG_BT_BNEP_DEBUG
========== BT_CMTP_DEBUG ==========
net/bluetooth/cmtp/capi.c:#ifndef CONFIG_BT_CMTP_DEBUG
net/bluetooth/cmtp/sock.c:#ifndef CONFIG_BT_CMTP_DEBUG
net/bluetooth/cmtp/core.c:#ifndef CONFIG_BT_CMTP_DEBUG
========== BT_HCI_CORE_DEBUG ==========
net/bluetooth/hci_core.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
net/bluetooth/hci_conn.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
net/bluetooth/hci_event.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
net/bluetooth/hci_sysfs.c:#ifndef CONFIG_BT_HCI_CORE_DEBUG
========== BT_HCI_SOCK_DEBUG ==========
net/bluetooth/hci_sock.c:#ifndef CONFIG_BT_HCI_SOCK_DEBUG
========== BT_HIDP_DEBUG ==========
net/bluetooth/hidp/sock.c:#ifndef CONFIG_BT_HIDP_DEBUG
net/bluetooth/hidp/core.c:#ifndef CONFIG_BT_HIDP_DEBUG
========== BT_L2CAP_DEBUG ==========
net/bluetooth/l2cap.c:#ifndef CONFIG_BT_L2CAP_DEBUG
========== BT_RFCOMM_DEBUG ==========
net/bluetooth/rfcomm/tty.c:#ifndef CONFIG_BT_RFCOMM_DEBUG
net/bluetooth/rfcomm/sock.c:#ifndef CONFIG_BT_RFCOMM_DEBUG
net/bluetooth/rfcomm/core.c:#ifndef CONFIG_BT_RFCOMM_DEBUG
========== BT_SCO_DEBUG ==========
net/bluetooth/sco.c:#ifndef CONFIG_BT_SCO_DEBUG
========== BT_SOCK_DEBUG ==========
net/bluetooth/af_bluetooth.c:#ifndef CONFIG_BT_SOCK_DEBUG
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
reply other threads:[~2007-05-02 19:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.0705021548050.16336@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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®