linux-kernel - Re: [PATCH V2 4/5] idle: Move idle conditions in cpuidle

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]

Message-ID: <20140224175838.GF9987@twins.programming.kicks-ass.net>
Date:	Mon, 24 Feb 2014 18:58:38 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Nicolas Pitre <nicolas.pitre@...aro.org>
Cc:	Daniel Lezcano <daniel.lezcano@...aro.org>, mingo@...nel.org,
	tglx@...utronix.de, rjw@...ysocki.net, preeti@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 4/5] idle: Move idle conditions in cpuidle_idle main
 function

On Mon, Feb 24, 2014 at 12:54:52PM -0500, Nicolas Pitre wrote:
> On Mon, 24 Feb 2014, Peter Zijlstra wrote:
> 
> > Urgh, looks like something went wrong with: cf37b6b48428d 
> > 
> > That commit doesn't actually remove kernel/cpu/idle.c nor is the new
> > code an exact replica of the old one.
> > 
> > Ingo, any chance we can get that fixed?
> 
> The patch I posted was based on v3.13.  It doesn't apply on later 
> kernels without a conflict.  I suspect the conflict resolution was 
> goofed somehow.

Jah, something went bad. I actually remember fixing that patch, but
clearly I must've made a massive fail someplace.
--
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/