linux-kernel - Re: [PATCH] NTP: Let update_persistent

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:	Mon, 9 Jun 2008 20:06:57 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alessandro Zummo <a.zummo@...ertech.it>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NTP: Let update_persistent_clock() sleep

Hi,

On Wed, 28 May 2008, Andrew Morton wrote:

> >  I am not sure who actually claims maintenance of kernel/time/ntp.c, but
> > it looks, Thomas, you seem to be our current time overseer -- could you
> > please speak out on this change?  I'd like this change to get applied
> > somewhere reasonable -- is it -mm?
> 
> Roman does most of the NTP work afaik.  I consider Thomas's git-hrt
> tree to be the route via which NTP changes get into linux-next and
> mainline.

That function is a little misplaced, we already have a driver/rtc dir, 
where this should go in the long term and ntp.c only providing the 
trigger, that time is stable. There it would also be possible to better 
take into account any quirks needed to update the chip.

bye, Roman
--
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/