DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
  b=I/G70BWbd5PsYGwNl32j0Tted4eoPA6/RcBM4SFV0gWdZ8RUi7I+NH6Q74i0TGvIg+fQe7D8mJnlY02Di6Lgx65ey4gEhPm7NK+93FonXq3tigs1unJpUCPTJPw6nBPiT5e+STf4KUZmGqxFhJnWxN/Femg2LZw0VfLjdqtgzvk=  ;
From: David Brownell <david-b@pacbell.net>
To: Tilman Schmidt <tilman@imap.cc>
Subject: Re: Kconfig RTC selection (was: 2.6.25-rc7: Ugh.)
Date: Fri, 28 Mar 2008 12:22:32 -0700
User-Agent: KMail/1.9.6
Cc: Ingo Molnar <mingo@elte.hu>, Mark Lord <lkml@rtr.ca>,
       David Miller <davem@davemloft.net>, jkosina@suse.cz, gregkh@suse.de,
       linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, pavel@suse.cz,
       akpm@linux-foundation.org, rtc-linux@googlegroups.com
References: <20080327160700.GB828@suse.de> <200803280249.42193.david-b@pacbell.net> <47ECE9BB.3050006@imap.cc>
In-Reply-To: <47ECE9BB.3050006@imap.cc>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803281222.33648.david-b@pacbell.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1795
Lines: 46

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/