Prev: [PATCH 05/11] Removing dead ETRAX_RS485_ON_PORT_G
Next: [PATCH 08/11] Removing dead ETRAX_SERIAL_PROC_ENTRY
From: Christoph Egger on 9 Jul 2010 09:50 Hi all! As part of the VAMOS[0] research project at the University of Erlangen we are looking at multiple integrity errors in linux' configuration system. I've been running a check on the arch/arm sourcetree for config Items not defined in Kconfig and found 33 such cases. Sourcecode blocks depending on these Items are not reachable from a vanilla kernel -- dead code. I've seen such dead blocks made on purpose e.g. while integrating new features into the kernel but generally they're just useless. Each of the patches in this patchset removes on such dead config Item, I'd be glad if you consider applying them. I've been doing deeper analysis of such issues before and can do so again but I'm not so sure they were fastly usefull. Unfortunately arm doesn't allow some allyesconfig build covering all of that code so I couldn't build-test all of them, sorry for that. Please keep me informed of this patch getting confirmed / merged so we can keep track of it. Regards Christoph Egger [0] http://vamos1.informatik.uni-erlangen.de/ Christoph Egger (11): Removing dead 68328_SERIAL_UART Removing dead CONSOLE_* Removing dead PP04 Removing dead (ALMA_ANS | DRAGONIXVZ | M68EZ328ADS) Removing dead ETRAX_RS485_ON_PORT_G Removing dead ETRAX_RS485_LTC1387 Removing dead ETRAX_EXTERN_PB6CLK_ENABLED Removing dead ETRAX_SERIAL_PROC_ENTRY Removing dead SERIAL_BFIN_{HARD_,}CTSRTS Removing dead SERIAL_BFIN_SPORT_CTSRTS Removing dead SERIAL_BFIN_SPORT_CONSOLE drivers/serial/68328serial.c | 16 ++---- drivers/serial/68328serial.h | 5 -- drivers/serial/68360serial.c | 26 +--------- drivers/serial/bfin_5xx.c | 103 -------------------------------------- drivers/serial/bfin_sport_uart.c | 100 ++----------------------------------- drivers/serial/crisv10.c | 71 -------------------------- 6 files changed, 12 insertions(+), 309 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |