| 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
| ||
|
Message-ID: <1363165170.3137.182.camel@x61.thuisdomein> Date: Wed, 13 Mar 2013 09:59:30 +0100 From: Paul Bolle <pebolle@...cali.nl> To: Ivo van Doorn <IvDoorn@...il.com>, Gertjan van Wingerde <gwingerde@...il.com>, Helmut Schaa <helmut.schaa@...glemail.com>, "John W. Linville" <linville@...driver.com> Cc: linux-wireless@...r.kernel.org, users@...x00.serialmonkey.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: rt2x00: Kconfig symbols RALINK_RT288X and RALINK_RT305X 0) Support for rt2800pci (or "the rt2860/rt3090 chipsets") was added in v2.6.33 (three years ago). References to the related Kconfig symbols RALINK_RT288X and RALINK_RT305X were introduced in that release. So were checks for their macros (CONFIG_RALINK_RT288X and CONFIG_RALINK_RT305X). 1) The Kconfig symbols themselves were never added in mainline. So these references and macros appear to be just markers for dead code in mainline, as that code will not be built. 2) This was previously discussed in https://lkml.org/lkml/2010/7/14/110 . The patch submitted in that message (which would remove all the dead code at the time) did not get applied. 3) What is the current status of the (out of tree) code that adds RALINK_RT288X and RALINK_RT305X? 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/
Powered by blists - more mailing lists