From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained Date: Tue, 20 Jun 2017 11:29:33 +0200 Message-ID: <20170620092933.m4pbbjcpw4zjas3i@pd.tnic> References: <20170619161323.pjdrh6l33pqix32x@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Thomas Gleixner Cc: "Shah, Nehal-bakulchandra" , LKML , Linus Walleij , "linux-gpio@vger.kernel.org" , "Xue, Ken" , "S-k, Shyam-sundar" , "stable@vger.kernel.org" List-Id: linux-gpio@vger.kernel.org On Tue, Jun 20, 2017 at 11:22:05AM +0200, Thomas Gleixner wrote: > If the interrupt _IS_ screaming because the hardware is buggered, then the > nobody cared thing will detect it and switch it off. That's all what we can > do, aside of not loading the driver at all. > > But that's way better than silently locking up the box forever. Sounds to me we should route this fix to stable. Looking at Linus' branch: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=fixes&id=ba714a9c1dea85e0bf2899d02dfeb9c70040427c patch isn't tagged for stable. Should it be? It certainly is an improvement of the situation. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.