linux-kernel - Re: 2.6.25-rc7: Ugh.

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080328102010.GA633@elte.hu>
Date:	Fri, 28 Mar 2008 11:20:10 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Brownell <david-b@...bell.net>
Cc:	Mark Lord <lkml@....ca>, David Miller <davem@...emloft.net>,
	jkosina@...e.cz, gregkh@...e.de, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, pavel@...e.cz,
	akpm@...ux-foundation.org, rtc-linux@...glegroups.com
Subject: Re: 2.6.25-rc7: Ugh.


* David Brownell <david-b@...bell.net> wrote:

> Prevent the most significant RTC configuration problems:
> 
>  - If the new RTC framework is enabled, don't allow any of the
>    legacy drivers to be configured.

yay!!!!

>  - When using generic RTC on x86, enable rtc-cmos by default.

Amen.

> It seems too many people are used to enabling a legacy RTC despite the 
> Kconfig help/comments; the gentle approach hasn't worked.

Very-Much-Acked-by: Ingo Molnar <mingo@...e.hu>

it's not just about being gentle: it's that there are thousands of 
.config options that are confusing to most users, so our defaults and 
rules must make sense. If we think that an approach is superior (which 
your new RTC code certainly is), we have to take up the responsibility 
of pushing that as a prominent, default choice and excluding the old 
code. That ends up benefiting everyone, reduces complexity of the 
kernel. You wont see anyone shed tears for the old code.

	Ingo
--
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/