linux-kernel - Re: [PATCH] fix RTC_CLASS regression with PARISC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Sep 2008 14:20:47 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	david-b@...bell.net
Cc:	rdunlap@...otime.net, akpm@...ux-foundation.org,
	James.Bottomley@...senpartnership.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-parisc@...r.kernel.org, alessandro.zummo@...ertech.it,
	tglx@...utronix.de
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC

From: David Brownell <david-b@...bell.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@...ux-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?
--
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/