linux-kernel - Re: [PATCH] Remove obsolete CLOCK_TICK

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080229140842.575e72aa.akpm@linux-foundation.org>
Date:	Fri, 29 Feb 2008 14:08:42 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	johnstul@...ibm.com, linux-kernel@...r.kernel.org, mingo@...e.hu,
	rostedt@...dmis.org
Subject: Re: [PATCH] Remove obsolete CLOCK_TICK_ADJUST

On Fri, 29 Feb 2008 05:49:35 +0100 (CET)
Roman Zippel <zippel@...ux-m68k.org> wrote:

> Can we please clean up the current mess and get the patch below merged?
> 
> bye, Roman
> 
> 
> Revert bbe4d18ac2e058c56adb0cd71f49d9ed3216a405 and
> e13a2e61dd5152f5499d2003470acf9c838eab84 and remove CLOCK_TICK_ADJUST
> completely. Add a optional kernel parameter ntp_tick_adj instead to allow
> adjusting of a large base drift and thus keeping ntpd happy.
> The CLOCK_TICK_ADJUST mechanism was introduced at a time PIT was the
> primary clock, but we have a varity of clock sources now, so a global PIT
> specific adjustment makes little sense anymore.
> 

The changelog provides no reason for the revert of those two patches.

Look at it from the point of view of a person who hasn't been following the
discussion (whose initials might be LT).  That person might get puzzled and
upset, no?

--
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/