From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:41796 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751212AbcIIQKG (ORCPT ); Fri, 9 Sep 2016 12:10:06 -0400 Date: Fri, 9 Sep 2016 18:10:10 +0200 From: Greg KH To: Fabio Estevam Cc: Marc Zyngier , stable , Fabio Estevam Subject: Re: [PATCH v2] irqchip/gic: Allow self-SGIs for SMP on UP configurations Message-ID: <20160909161010.GA21271@kroah.com> References: <1473428682-14552-1-git-send-email-festevam@gmail.com> <57D2C9F1.5070900@arm.com> <57D2D868.7090205@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Fri, Sep 09, 2016 at 12:48:34PM -0300, Fabio Estevam wrote: > Hi Marc, > > On Fri, Sep 9, 2016 at 12:42 PM, Marc Zyngier wrote: > > >> Without this patch imx6ul SoC hangs after a 'reboot' command. > > > > But that's not a regression, right? It *never* worked before, as far as > > I know, because we never supported such a configuration in the past. > > imx6ul is supported since kernel 4.3. > > > I'm a bit concerned when I see backporting random patches to random > > kernel versions for things that are not bugs. I'll leave it up to Greg > > to decide, but I thought I should point out what this patch actually is. > > Not bugs? I consider the hang I get after running 'reboot' on imx6ul a bug. > > According to Documentation/stable_kernel_rules.txt : > > " - It must fix a problem that causes a build error (but not for things > marked CONFIG_BROKEN), an oops, a hang, data corruption, a real > security issue, or some "oh, that's not good" issue. In short, something > critical. " > > , so that's why I submitted for stable inclusion. But if it never worked to start with, that's not really a regression, that is a "make new hardware work" type thing. Did it work properly in 4.3? What caused support for this hardware to break? thanks, greg k-h