| 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: <20080219101246.GB2202@elf.ucw.cz> Date: Tue, 19 Feb 2008 11:12:46 +0100 From: Pavel Machek <pavel@....cz> To: David Brownell <david-b@...bell.net> Cc: kernel list <linux-kernel@...r.kernel.org> Subject: Re: WARN_ON(): proc_dir_entry 'rtc' already registered On Mon 2008-02-18 03:08:16, David Brownell wrote: > On Monday 18 February 2008, Pavel Machek wrote: > > > How to fix ... how about: instead of just warning folk > > > off such legacy RTC drivers [1] we just wrap them with > > > an "if RTC_LIB != n" so this mistake won't be possible. > > > > Yes, disabling bad configs in Kconfig seems like way to go. > > Problem is ... that also disables valid configs that > get assembled by picking the right module(s) for the > target system. Is there any reason to use the old rtc subsystem? At least OLD_RTC=y NEW_RTC=y should be disabled... even if OLD_RTC=m NEW_RTC=m makes some sense. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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