From: David Miller <davem@davemloft.net>
To: david-b@pacbell.net
Cc: rdunlap@xenotime.net, akpm@linux-foundation.org,
James.Bottomley@hansenpartnership.com,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-parisc@vger.kernel.org, alessandro.zummo@towertech.it,
tglx@linutronix.de
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Wed, 10 Sep 2008 14:20:47 -0700 (PDT) [thread overview]
Message-ID: <20080910.142047.265458325.davem@davemloft.net> (raw)
In-Reply-To: <200809101419.05499.david-b@pacbell.net>
From: David Brownell <david-b@pacbell.net>
Date: Wed, 10 Sep 2008 14:19:04 -0700
> On Wednesday 10 September 2008, Randy.Dunlap wrote:
> >
> > > > > =============== CUT ON THE DOTTED LINE ==================
> > > > > Subject: ntp: let update_persistent_clock() sleep
> > > > > From: "Maciej W. Rozycki" <macro@linux-mips.org>
> > > >
> > > > I see, as Paul mentioned this is needed for stuff like RTCs
> > > > behind I2C.
> > > >
> > > > This change isn't in Linus's tree yet.
> > >
> > > Should it be?
>
> IMO if it doesn't make 2.6.27, it should merge for 2.6.28 early-ish.
>
>
> > > Its current status is: stuck in -mm. I've sent it to Thomas a couple
> > > of times marked "for 2.6.27?" and he might have applied it now (I'm a
> > > few days behind, waiting for linux-next to start up again).
> >
> > This is something that you can attempt (again) to address next week along
> > with other process issues...
>
> I don't think anyone in particular has been _pushing_ to resolve these
> NTP related issues ... lack of urgency. Maybe it's fair to think of
> that as a process issue. If DaveM wants SPARC64 to completely remove
> its legacy RTC support for some release (which?) then: (a) great! and
> (b) that should be sufficient urgency.
Well, firstly my RTC sparc work is 2.6.28 targetted.
Secondly, that sleeping capability is only really needed for I2C based
RTC chips, of which sparc isn't currently making any use of.
PowerPC folks do, however, use I2C based RTC chips right now I thought?
next prev parent reply other threads:[~2008-09-10 21:21 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 [this message]
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
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=20080910.142047.265458325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=alessandro.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--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