[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <673c215c-54e3-ffdd-7537-bec469f068a7@roeck-us.net>
Date: Sun, 5 Feb 2017 07:00:42 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Borislav Petkov <bp@...en8.de>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Mark Brown <broonie@...nel.org>,
Fengguang Wu <fengguang.wu@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
X86 ML <x86@...nel.org>, Andy Lutomirski <luto@...capital.net>
Subject: Re: Regression on next-20170203 spi/for-next 3f87493930a0f qemu on
x86_64
On 02/05/2017 02:33 AM, Borislav Petkov wrote:
> On Sat, Feb 04, 2017 at 05:22:55PM -0800, Guenter Roeck wrote:
>> Upstream (v4.10-rc6-193-ga572a1b99948), the same command yields no error at all:
>
> That's because you tested Linus' merge commit of the branch which fixed that :-)
>
FWIW, I also tested v4.10-rc3, which didn't have the problem either.
> IOW, the fix should be:
>
> aaaec6fc7554 ("x86/irq: Make irq activate operations symmetric")
>
Yes, it does. Let's hope that this fixes Luis' problem as well.
Thanks,
Guenter
Powered by blists - more mailing lists