linux-kernel - ARCH_PXA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1321351777.20271.166.camel@x61.thuisdomein>
Date:	Tue, 15 Nov 2011 11:09:37 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Thierry Reding <thierry.reding@...onic-design.de>,
	Richard Purdie <rpurdie@...ux.intel.com>,
	Russell King <rmk+kernel@....linux.org.uk>,
	Wim Van Sebroeck <wim@...ana.be>
Cc:	linux-kernel@...r.kernel.org
Subject: ARCH_PXA_ADX

0) Since v2.6.32 the mainline tree supports the "Avionic Design Xanthos
Backlight Driver" (BACKLIGHT_ADX) and the "Avionic Design Xanthos
watchdog" driver (ADX_WATCHDOG). These were added in commit 3b96ea9ef8
("[...] Add support for the Avionic Design Xanthos backlight device.")
and 38461c5c08 ("[...] Add support for the Avionic Design Xanthos
watchdog timer.").

1) Both drivers' Kconfig symbols depend on the Kconfig symbol
ARCH_PXA_ADX. At that time this symbol didn't exist. It still doesn't. I
haven't been able to find anything remotely related (ie, I even did
things like "git grep -i PXA | grep -i ADX").

2) So it seems these two drivers could never have been built from the
mainline tree. (I'm starting to think that the config tools should
somehow check stuff like this.)

3) Is the above correct? If it is, why shouldn't I submit the trivial
patch to remove both these drivers?

Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/