Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1670546
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained |
| Date | 2017-06-20 11:40 +0200 |
| Message-ID | <tUnNF-6PZ-39@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <tLfvX-1kn-1@gated-at.bofh.it> <tLhep-2se-1@gated-at.bofh.it> <tLjSW-490-25@gated-at.bofh.it> <tU7zc-4Y3-3@gated-at.bofh.it> <tUnDX-6Ll-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained Thomas Gleixner <tglx@linutronix.de> - 2017-06-20 11:30 +0200 Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained Borislav Petkov <bp@alien8.de> - 2017-06-20 11:40 +0200
csiph-web