[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47ECF753.1070804@rtr.ca>
Date: Fri, 28 Mar 2008 09:49:07 -0400
From: Mark Lord <lkml@....ca>
To: Tilman Schmidt <tilman@...p.cc>
Cc: David Brownell <david-b@...bell.net>, Ingo Molnar <mingo@...e.hu>,
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
Tilman Schmidt wrote:
> On Fri, 28 Mar 2008 02:49:41 -0700, David Brownell wrote:
>> It seems too many people are used to enabling a legacy RTC despite the
>> Kconfig help/comments; the gentle approach hasn't worked.
>
> Gentleness is not the point. The Kconfig help/comments where just
> not clear at all.
>
> 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. 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)
> - noting explicitly which of the two RTC options is the "legacy"
> one (is it RTC_CLASS?)
> - enhancing the conflict message, which reads, in git-current:
> *** Conflicting RTC option has been selected, check GEN_RTC
> *** RTC interfaces ***
..
Exactly the issue. Mod++++++++++++++++++++++
--
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