On Wed, Jun 21, 2017 at 06:37:09PM +0200, Linus Walleij wrote:
> This is sent to Torvalds, but you can simply suggest to Greg to pick
> this for stable according to the process in:
> Documentation/process/stable-kernel-rules.rst
Yeah, I saw your pull request after hitting send. I'll send it to Gre
On Tue, Jun 20, 2017 at 2:28 PM, Borislav Petkov wrote:
> On Mon, May 29, 2017 at 01:55:57PM +0200, Linus Walleij wrote:
>> Patch applied for fixes.
>
> Btw, any chance you can add the CC:stable tag to it or would you prefer
> for me to backport it once it hits mainline?
This is sent to Torvalds,
On Mon, May 29, 2017 at 01:55:57PM +0200, Linus Walleij wrote:
> Patch applied for fixes.
Btw, any chance you can add the CC:stable tag to it or would you prefer
for me to backport it once it hits mainline?
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting
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 s
On Mon, 19 Jun 2017, Borislav Petkov wrote:
> On Fri, May 26, 2017 at 09:33:10AM +, Shah, Nehal-bakulchandra wrote:
> > Hi Thomas,
> >
> > Thanks for the prompt reply. Agree on points.
> >
> > we will validate at our end and shall provide the update.
>
> Any news on the issue? Resolution?
On Fri, May 26, 2017 at 09:33:10AM +, Shah, Nehal-bakulchandra wrote:
> Hi Thomas,
>
> Thanks for the prompt reply. Agree on points.
>
> we will validate at our end and shall provide the update.
Any news on the issue? Resolution?
I still have a user reporting "irq 7: nobody cared (try boot
On Mon, 29 May 2017, Linus Walleij wrote:
> On Tue, May 23, 2017 at 11:23 PM, Thomas Gleixner wrote:
>
> > The AMD pinctrl driver uses a chained interrupt to demultiplex the GPIO
> > interrupts. Kevin Vandeventer reported, that his new AMD Ryzen locks up
> > hard on boot when the AMD pinctrl dri
On Tue, May 23, 2017 at 11:23 PM, Thomas Gleixner wrote:
> The AMD pinctrl driver uses a chained interrupt to demultiplex the GPIO
> interrupts. Kevin Vandeventer reported, that his new AMD Ryzen locks up
> hard on boot when the AMD pinctrl driver is initialized. The reason is an
> interrupt stor
On Fri, May 26, 2017 at 09:33:10AM +, Shah, Nehal-bakulchandra wrote:
> Hi Thomas,
>
> Thanks for the prompt reply. Agree on points.
>
> we will validate at our end and shall provide the update.
First of all, please do not top-post.
What update are you talking about? The patch needs to go
; linux-g...@vger.kernel.org; Borislav Petkov
; Xue, Ken ; S-k, Shyam-sundar
; sta...@vger.kernel.org
Subject: RE: [PATCH] pinctrl/amd: Use regular interrupt instead of chained
Nehal,
On Fri, 26 May 2017, Shah, Nehal-bakulchandra wrote:
> Thanks for the patch. However, we have received this is
Nehal,
On Fri, 26 May 2017, Shah, Nehal-bakulchandra wrote:
> Thanks for the patch. However, we have received this issue from multiple
> people and different disro but it occurs only on Gigabyte hardware. With
> reference AM4 ryzen board we are not facing this issue. We are in
> discussion with g
Hi Thomas,
Thanks for the patch. However, we have received this issue from multiple people
and different disro but it occurs only on Gigabyte hardware. With reference AM4
ryzen board we are not facing this issue.
We are in discussion with gigabyte to check the BIOS part. Once we have clarity
on
12 matches
Mail list logo
