From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751044AbcGNHrY (ORCPT ); Thu, 14 Jul 2016 03:47:24 -0400 Received: from mail-wm0-f65.google.com ([74.125.82.65]:33256 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750829AbcGNHrS (ORCPT ); Thu, 14 Jul 2016 03:47:18 -0400 Date: Thu, 14 Jul 2016 09:47:13 +0200 From: Ingo Molnar To: Jacek Anaszewski Cc: Anna-Maria Gleixner , LKML , Peter Zijlstra , Thomas Gleixner , rt@linutronix.de, Richard Cochran , Sebastian Andrzej Siewior , Linus Torvalds , Linus Walleij , Paul Gortmaker , Richard Purdie , linux-leds@vger.kernel.org Subject: Re: [patch V2 43/67] leds/trigger/cpu: Convert to hotplug state machine Message-ID: <20160714074713.GA17287@gmail.com> References: <20160713153219.128052238@linutronix.de> <20160713153336.465496902@linutronix.de> <57873CFF.1010803@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57873CFF.1010803@samsung.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jacek Anaszewski 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? > > + */ > > Why wasn't it possible to clarify the issue before the > submission? Nothing has been applied yet (this submission is part of the clarification process), are you fine with this conversion as-is, with a separate patch doing any followup fixes - or would you prefer another approach? This CPU hotplug series tries to do straightforward conversions to the CPU hotplug state machine without changing behavior - while pointing out any problems that were found along the way. I agree that the addition of this FIXME should probably have been pointed out in the changelog as well, but this patch was submitted once already with no feedback received - and that's the historic pattern with such types of series: only a low percentage of all driver maintainers replies so we have to be proactive to a certain degree to have a chance of improving core kernel infrastructure. It's better to add FIXMEs with open questions that to introduce subtle problems. Thanks, Ingo