From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Brownell <david-b@pacbell.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Mon, 08 Sep 2008 16:37:40 -0500 [thread overview]
Message-ID: <1220909860.8074.77.camel@localhost.localdomain> (raw)
In-Reply-To: <200809081429.57805.david-b@pacbell.net>
On Mon, 2008-09-08 at 14:29 -0700, David Brownell wrote:
> > No, it's a regression. ... This turns off the ability to select
> > GEN_RTC if you've said yes to RTC_CLASS. Since RTC_CLASS is currently
> > unsupported on parisc, we need to fix that by making the RTC_CLASS
> > option unselectable on parisc.
>
> So you affirmed that there was no override, AND that it was
> previously treated as junk DNA (ignored). So just what were
> you disagreeing with me about??
The fact that the override you put in to disable GEN_RTC is causing a
regression.
> I have a hard time calling something a regression which
> was never really a supported configuration. And which
> still *JUST WORKS* in those defconfigs ... given all that,
> it's hard to argue that something is actually broken.
On 2.6.25 the parisc users got a working realtime clock. On 2.6.26 they
can find themselves without one using the same .config file. This is
the regression. The fix is to disable RTC_CLASS until we have it
working for parisc.
> Kconfig is not about letting Aunt Tillie configure kernels
> without being able to shoot herself in the foot. That
> discussion has been had (at length!) before. Result, we
> have a much better kernel config framework ... but still
> don't facilitate "Kconfig-4-dummiez" audiences.
Kconfig is complex enough that we try not to trip users up by hiding
things, especially when it's the wrong thing to hide on this platform.
If an option specifically doesn't work or causes harm on a platform, it
shouldn't be selectable on that platform. This isn't Aunt Tillieism,
this is called common sense.
James
prev parent reply other threads:[~2008-09-08 21:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 15:53 [PATCH] fix RTC_CLASS regression with PARISC James Bottomley
2008-09-08 18:19 ` David Brownell
2008-09-08 18:39 ` James Bottomley
2008-09-08 19:13 ` David Brownell
2008-09-08 20:28 ` James Bottomley
2008-09-08 21:29 ` David Brownell
2008-09-08 21:35 ` David Miller
2008-09-08 23:00 ` James Bottomley
2008-09-08 23:04 ` David Miller
2008-09-08 23:23 ` James Bottomley
2008-09-08 23:32 ` David Brownell
2008-09-08 23:43 ` David Miller
2008-09-08 23:29 ` David Brownell
2008-09-08 23:44 ` David Miller
2008-09-09 0:55 ` David Brownell
2008-09-09 2:52 ` David Miller
2008-09-09 3:17 ` David Brownell
2008-09-09 3:51 ` David Miller
2008-09-09 4:14 ` David Brownell
2008-09-10 21:04 ` Andrew Morton
2008-09-10 21:09 ` Randy.Dunlap
2008-09-10 21:19 ` David Brownell
2008-09-10 21:20 ` David Miller
2008-09-10 21:36 ` David Brownell
2008-09-10 21:40 ` David Miller
2008-09-09 1:22 ` Paul Mackerras
2008-09-08 21:37 ` James Bottomley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1220909860.8074.77.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox