linux-kernel - Re: Kconfig RTC selection (was: 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: <200803281222.33648.david-b@pacbell.net>
Date:	Fri, 28 Mar 2008 12:22:32 -0700
From:	David Brownell <david-b@...bell.net>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	Ingo Molnar <mingo@...e.hu>, 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: Kconfig RTC selection (was: 2.6.25-rc7: Ugh.)

On Friday 28 March 2008, Tilman Schmidt wrote:
> 
> FWIW, it's still confusing to have an option "Enhanced Real Time
> Clock Support" under "Character Devices", then later an option
> "Real Time Clock" one level higher, none of the two in any way
> acknowledging the existence of the other one, and only after
> naively selecting both, you are told that there is some sort of
> conflict.

You mean "still, after applying that patch I sent"?  I don't
see how that could be; it doesn't allow both to be selected.


> Couldn't this be made more explicit, such as: 
> - mentioning in both options' help text that the other one
>    shouldn't be selected at the same time (if that's true)

I think that'd be more confusing, since it's not possible.
Telling people not to do something will usually make them
think it's possible ...


> - noting explicitly which of the two RTC options is the "legacy"
>    one (is it RTC_CLASS?)

That term isn't visible through the Kconfig user interfaces,
so I'm not sure why it should be introduced except as part
of a strategy to get rid of all those old drivers.  Which is
probably worth having, but isn't waht that patch addressed!


> - enhancing the conflict message, which reads, in git-current:
>         *** Conflicting RTC option has been selected, check GEN_RTC
>         *** RTC interfaces ***
>    Perhaps it's only me, but I do not know what to make of this.

Me either, since the patch I sent removed that message.
I'm now quite sure you did *NOT* apply and try that patch
before responding to it.

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