mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>, Andy Lutomirski <luto@amacapital.net>
Subject: Re: Regression on next-20170203 spi/for-next 3f87493930a0f qemu on x86_64
Date: Mon, 6 Feb 2017 18:47:43 +0100	[thread overview]
Message-ID: <20170206174743.GA24047@wotan.suse.de> (raw)
In-Reply-To: <20170205103325.w5qnzmzveowwkbks@pd.tnic>

On Sun, Feb 05, 2017 at 11:33:25AM +0100, 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 :-)
> 
> IOW, the fix should be:
> 
> aaaec6fc7554 ("x86/irq: Make irq activate operations symmetric")
> 
> It is on its way to stable too, as we speak.

I've taken this patch and applied it on top of next-20170203
and confirm it fixes the regression. I've also tested next-20170206
which has the fix and confirm that boots as well.

Do we have any test units which can kick off regularly to test against such
type of regression in the future or is it not worth it?

Thanks Boris!

  Luis

  parent reply	other threads:[~2017-02-06 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-04 20:05 Luis R. Rodriguez
2017-02-04 23:17 ` Stephen Rothwell
2017-02-04 23:27   ` Stephen Rothwell
2017-02-05 13:59   ` Mark Brown
2017-02-05  1:22 ` Guenter Roeck
2017-02-05 10:33   ` Borislav Petkov
2017-02-05 15:00     ` Guenter Roeck
2017-02-06 17:47     ` Luis R. Rodriguez [this message]
2017-02-07  0:02       ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170206174743.GA24047@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=bp@alien8.de \
    --cc=broonie@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=luto@amacapital.net \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®