[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160714094154.GY30154@twins.programming.kicks-ass.net>
Date: Thu, 14 Jul 2016 11:41:54 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Jacek Anaszewski <j.anaszewski@...sung.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Anna-Maria Gleixner <anna-maria@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>, rt@...utronix.de,
Richard Cochran <rcochran@...utronix.de>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linus Walleij <linus.walleij@...aro.org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Richard Purdie <rpurdie@...ys.net>, linux-leds@...r.kernel.org
Subject: Re: [patch V2 43/67] leds/trigger/cpu: Convert to hotplug state
machine
On Thu, Jul 14, 2016 at 10:10:55AM +0200, Jacek Anaszewski wrote:
> On 07/14/2016 09:47 AM, Ingo Molnar wrote:
> >
> >* Jacek Anaszewski <j.anaszewski@...sung.com> wrote:
> >
> >>>@@ -133,7 +125,13 @@ static int __init ledtrig_cpu_init(void)
> >>> }
> >>>
> >>> register_syscore_ops(&ledtrig_cpu_syscore_ops);
> >>>- register_cpu_notifier(&ledtrig_cpu_nb);
> >>>+
> >>>+ /*
> >>>+ * FIXME: Why needs this to happen in the interrupt disabled
> >>>+ * low level bringup phase of a cpu?
> >>>+ */
> Thanks for the explanation. I'm OK with that approach.
Since we have your attention, could you perhaps attempt to answer the
question so we can fix the fixme?
Powered by blists - more mailing lists