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] [day] [month] [year] [list]
Message-ID: <20081210041943.GA27356@linux-sh.org>
Date:	Wed, 10 Dec 2008 13:19:43 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	john stultz <johnstul@...ibm.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, rmk+lkml@....linux.org.uk,
	cooloney@...nel.org, starvik@...s.com, takata@...ux-m32r.org,
	geert@...ux-m68k.org, Roman Zippel <zippel@...ux-m68k.org>,
	Magnus Damm <magnus.damm@...il.com>, wli@...omorphy.com,
	chris@...kel.net, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC][PATCH 2/3] Convert !GENERIC_TIME arches to use arch_getoffset() infrastructure.

On Mon, Dec 08, 2008 at 07:51:07PM -0800, john stultz wrote:
> This converts the following arches to use the arch_getoffset()
> infrastructure, finally bringing them into the GENERIC_TIME fold:
> 
> arm
> blackfin
> cris
> m32r
> m68k
> sh
> sparc
> xtensa
> 
> I have split out patches for each arch, but I'm sending out the
> megapatch to keep the RFC patchlist short.
> 
> I do not have cross compilers for these architectures, and in some cases
> (like arm, and sh) the architectures can be compiles both with and
> without clocksources. So I've taken my best swing at converting this,
> but I'm not confident I got it right. Any assistance from arch
> maintainers or testers would be great.
> 
> Signed-off-by: John Stultz <johnstul@...ibm.com>
> 
Just got around to testing the SH bits, works fine in both
configurations.

Acked-by: Paul Mundt <lethal@...ux-sh.org>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ