All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	James.Bottomley@hansenpartnership.com,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-parisc@vger.kernel.org, alessandro.zummo@towertech.it,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Wed, 10 Sep 2008 14:19:04 -0700	[thread overview]
Message-ID: <200809101419.05499.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0809101407490.7159@shark.he.net>

On Wednesday 10 September 2008, Randy.Dunlap wrote:
>=20
> > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CUT ON THE DOTTED=
 LINE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > Subject: ntp: let update_persistent_clock() sleep
> > > > From: "Maciej W. Rozycki" <macro@linux-mips.org>
> > >=20
> > > I see, as Paul mentioned this is needed for stuff like RTCs
> > > behind I2C.
> > >=20
> > > This change isn't in Linus's tree yet.
> >=20
> > Should it be?

IMO if it doesn't make 2.6.27, it should merge for 2.6.28 early-ish.

=20
> > Its current status is: stuck in -mm. =A0I've sent it to Thomas a co=
uple
> > 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).
>=20
> This is something that you can attempt (again) to address next week a=
long
> 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.

There was, I think, another patch related to this one.  Then there may
be a few other loose ends to tie up also.

- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
 in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	James.Bottomley@hansenpartnership.com,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-parisc@vger.kernel.org, alessandro.zummo@towertech.it,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Wed, 10 Sep 2008 14:19:04 -0700	[thread overview]
Message-ID: <200809101419.05499.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0809101407490.7159@shark.he.net>

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.

There was, I think, another patch related to this one.  Then there may
be a few other loose ends to tie up also.

- Dave

  reply	other threads:[~2008-09-10 21:19 UTC|newest]

Thread overview: 35+ 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: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: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:17                           ` David Brownell
2008-09-09  3:51                           ` David Miller
2008-09-09  3:51                             ` David Miller
2008-09-09  4:14                             ` David Brownell
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 [this message]
2008-09-10 21:19                               ` David Brownell
2008-09-10 21:20                               ` David Miller
2008-09-10 21:20                                 ` David Miller
2008-09-10 21:36                                 ` David Brownell
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=200809101419.05499.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=alessandro.zummo@towertech.it \
    --cc=davem@davemloft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.