On Wed, 2 Mar 2016, Peter Zijlstra wrote: > 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@xxxxxxxxxxxxx> > > AuthorDate: Fri, 26 Feb 2016 18:43:32 +0000 > > Committer: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > > 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? Yes, the current state is more or less wrapping the existing notifiers and stopping them is not a brilliant idea. I've tried and it exploded nicely in my face. The ones we convert over to the state machine will be stoppable and reversible. And at the end the notifiers will be gone and with them the can't stop stuff, except maybe for a few crucial points. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|