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
| ||
|
Date: Mon, 22 Apr 2013 16:51:47 +0100 From: Mark Rutland <mark.rutland@....com> To: Stephen Boyd <sboyd@...eaurora.org> Cc: Rob Herring <robherring2@...il.com>, Russell King <linux@....linux.org.uk>, "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>, Will Deacon <Will.Deacon@....com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "arm@...nel.org" <arm@...nel.org>, John Stultz <john.stultz@...aro.org>, Catalin Marinas <Catalin.Marinas@....com>, Thomas Gleixner <tglx@...utronix.de>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH 0/4] ARM 64 bit sched_clock take #2 On Mon, Apr 22, 2013 at 04:36:14PM +0100, Stephen Boyd wrote: > On 04/22/13 08:34, Mark Rutland wrote: > > Hi Stephen, > > > > On Sat, Apr 20, 2013 at 01:29:02AM +0100, Stephen Boyd wrote: > >> This is what I was thinking. I don't see why we can't move this to generic > >> code and have arm64 use it too. Those patches will follow once I find an > >> arm64 compiler. > >> > >> First two patches should probably go in even if the 64 bit stuff doesn't go in > >> at the same time. > >> > >> Stephen Boyd (4): > >> ARM: sched_clock: Remove unused needs_suspend member > >> ARM: sched_clock: Return suspended count earlier > >> ARM: sched_clock: Add support for >32 bit sched_clock > >> ARM: arch_timer: Move to setup_sched_clock_64() > >> > >> arch/arm/include/asm/sched_clock.h | 5 +- > >> arch/arm/kernel/arch_timer.c | 14 +---- > >> arch/arm/kernel/sched_clock.c | 111 ++++++++++++++++++++++++++----------- > >> 3 files changed, 84 insertions(+), 46 deletions(-) > > I wanted to look at the series with more context, but I don't seem to be able > > to apply patch 2 and beyond to my tree, and I couldn't figure out what tree > > this series was based on. > > > > What do I need to use as the base for this series? > > These are based on next-20130419. Cheers! Mark. -- 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