From: Robert P. J. Day <rpjday@crashcourse.ca>
To: b43-dev@lists.infradead.org
Subject: leftover b43-related cruft in drivers/net/wireless?
Date: Thu, 18 Sep 2014 05:02:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1409180459100.16448@localhost> (raw)
i have a shell script that scans selected parts of the kernel source
tree to locate, among other things, unused config variables in
Kconfig files, and it identified the following under
drivers/net/wireless:
$ find_unused_configs.sh drivers/net/wireless
>>>>> B43_BCMA_PIO
drivers/net/wireless/b43/Kconfig:113:config B43_BCMA_PIO
>>>>> B43_BUSES_SSB
drivers/net/wireless/b43/Kconfig:52:config B43_BUSES_SSB
>>>>> B43LEGACY_DMA_MODE
drivers/net/wireless/b43legacy/Kconfig:85:config B43LEGACY_DMA_MODE
>>>>> B43LEGACY_PCICORE_AUTOSELECT
drivers/net/wireless/b43legacy/Kconfig:31:config B43LEGACY_PCICORE_AUTOSELECT
>>>>> B43LEGACY_PIO_MODE
drivers/net/wireless/b43legacy/Kconfig:92:config B43LEGACY_PIO_MODE
>>>>> B43_PCICORE_AUTOSELECT
drivers/net/wireless/b43/Kconfig:68:config B43_PCICORE_AUTOSELECT
>>>>> B43_PIO
drivers/net/wireless/b43/Kconfig:119:config B43_PIO
$
no real harm, just means that there are Kconfig definitions of the
above variables that no one appears to be testing for in the entire
kernel source tree, so they're potentially safe to be removed.
feel free to do with that what you will.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-09-18 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 9:02 Robert P. J. Day [this message]
2014-09-18 9:17 ` leftover b43-related cruft in drivers/net/wireless? Rafał Miłecki
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=alpine.LFD.2.11.1409180459100.16448@localhost \
--to=rpjday@crashcourse.ca \
--cc=b43-dev@lists.infradead.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 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.