From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: dead CONFIG_ variables: drivers/video/
Date: Thu, 3 May 2007 06:40:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705030638270.380@localhost.localdomain> (raw)
$ ../dead_config.sh drivers/video
========== FB_68328_INVERT ==========
drivers/video/68328fb.c:53:#if defined(CONFIG_FB_68328_INVERT)
========== FB_AU1200_DEVS ==========
drivers/video/au1200fb.c:52:#ifndef CONFIG_FB_AU1200_DEVS
drivers/video/au1200fb.c:53:#define CONFIG_FB_AU1200_DEVS 4
drivers/video/au1200fb.c:160:static struct au1200fb_device _au1200fb_devices[CONFIG_FB_AU1200_DEVS];
drivers/video/au1200fb.c:714: for (i = 0; i < CONFIG_FB_AU1200_DEVS; ++i) {
drivers/video/au1200fb.c:1635: for (plane = 0; plane < CONFIG_FB_AU1200_DEVS; ++plane) {
drivers/video/au1200fb.c:1730: for (plane = 0; plane < CONFIG_FB_AU1200_DEVS; ++plane)
drivers/video/au1200fb.c:1850: for (plane = 0; plane < CONFIG_FB_AU1200_DEVS; ++plane) {
========== FB_MATROX_32MB ==========
drivers/video/matrox/matroxfb_base.c:307:#ifdef CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_base.c:327:#ifdef CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_base.c:339:#ifdef CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_base.c:1342:#ifdef CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_base.c:1619:#ifdef CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_DAC1064.c:1053:#ifdef CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_base.h:58:#define CONFIG_FB_MATROX_32MB
drivers/video/matrox/matroxfb_base.h:466:#ifdef CONFIG_FB_MATROX_32MB
========== FB_NVIDIA_DEBUG ==========
drivers/video/nvidia/nvidia.c:40:#undef CONFIG_FB_NVIDIA_DEBUG
drivers/video/nvidia/nvidia.c:41:#ifdef CONFIG_FB_NVIDIA_DEBUG
drivers/video/nvidia/nvidia.c:50:#ifdef CONFIG_FB_NVIDIA_DEBUG
========== FB_SOFT_CURSOR ==========
drivers/video/sis/sis_main.c:1906:#ifdef CONFIG_FB_SOFT_CURSOR
========== MACH_MX1FS2 ==========
drivers/video/imxfb.c:410:#ifndef CONFIG_MACH_MX1FS2
arch/arm/tools/mach-types:486:mx1fs2 MACH_MX1FS2 MX1FS2 470
========== MACH_PIMX1 ==========
drivers/video/imxfb.c:404:#ifndef CONFIG_MACH_PIMX1
arch/arm/tools/mach-types:678:pimx1 MACH_PIMX1 PIMX1 664
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next reply other threads:[~2007-05-03 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 10:40 Robert P. J. Day [this message]
2007-05-03 11:16 ` Russell King
2007-05-03 14:16 ` Sascha Hauer
2007-05-03 12:04 ` Antonino A. Daplas
2007-05-03 12:35 ` Robert P. J. Day
2007-05-03 13:19 ` Antonino A. Daplas
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.0705030638270.380@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®