On Fri, Sep 09, 2016 at 05:06:02PM +0100, Marc Zyngier wrote: > On 09/09/16 16:48, Fabio Estevam wrote: > > Hi Marc, > > > > On Fri, Sep 9, 2016 at 12:42 PM, Marc Zyngier <marc.zyngier@xxxxxxx> 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. > > And yet nobody reported this as an issue until the 4.8 cycle. So it > doesn't look like it was annoying anyone until then. > > > > >> 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. > > > > I don't, which is why I didn't tag it for stable the first place. I > consider this as an unsupported configuration (MP CPU on a UP GIC), > which we start supporting from 4.8 onward. > > Anyway, I'm not going to argue any further for such a small patch, but > I've made my position clear. As the maintainer wants this removed, I've now dropped it from the 4.7-stable queue. Fabio, just use 4.8 on this hardware and you should be fine. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html