[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160302124138.GF6357@twins.programming.kicks-ass.net>
Date: Wed, 2 Mar 2016 13:41:38 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: rostedt@...dmis.org, tglx@...utronix.de, riel@...hat.com,
mingo@...nel.org, rafael.j.wysocki@...el.com,
bigeasy@...utronix.de, arjan@...ux.intel.com,
rusty@...tcorp.com.au, torvalds@...ux-foundation.org,
hpa@...or.com, srivatsa@....edu, pjt@...gle.com, tj@...nel.org,
akpm@...ux-foundation.org, oleg@...hat.com,
linux-kernel@...r.kernel.org, paulmck@...ux.vnet.ibm.com
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:smp/hotplug] cpu/hotplug: Make target state writeable
On Tue, Mar 01, 2016 at 11:55:01AM -0800, tip-bot for Thomas Gleixner wrote:
> Commit-ID: 757c989b9994f51b42d6be1bd33c7c12d16a3ac7
> Gitweb: http://git.kernel.org/tip/757c989b9994f51b42d6be1bd33c7c12d16a3ac7
> Author: Thomas Gleixner <tglx@...utronix.de>
> AuthorDate: Fri, 26 Feb 2016 18:43:32 +0000
> Committer: Thomas Gleixner <tglx@...utronix.de>
> CommitDate: Tue, 1 Mar 2016 20:36:55 +0100
>
> cpu/hotplug: Make target state writeable
>
> Make it possible to write a target state to the per cpu state file, so we can
> switch between states.
But you've marked nearly all of them cant_stop, so while this implements
the interface, its not really functional just yet, right?
Powered by blists - more mailing lists