mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Merkey <linux.mdb@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	X86 ML <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Borislav Petkov <bp@alien8.de>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [GIT PULL] please pull one bug fix for v4.4
Date: Mon, 11 Jan 2016 21:58:09 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1601112156530.3575@nanos> (raw)
In-Reply-To: <CA+55aFw=0Z9zSa26BPxOw0-A9K0CWGjDYTu=6XrXTVmQpvW8eQ@mail.gmail.com>

On Mon, 11 Jan 2016, Linus Torvalds wrote:

> The merge window is open, so I started looking at this that I had
> ignored as being too late last time..
> 
> On Sun, Dec 13, 2015 at 7:02 PM, Jeff Merkey <linux.mdb@gmail.com> wrote:
> > Patch address with email included:
> >
> > https://github.com/jeffmerkey/linux/commit/e1d3c76814c839a835286843f0bca33b0c5d0dd8.patch
> 
> So at a minimum, I'd like a sign-off for the patch. But also, can you
> describe how to actually trigger the problem? Is this actually
> triggerable without an ICE?

This patch has been discussed and the version above has issues. It's still not
decided how we are going to deal with that.

Thanks,

	tglx

  reply	other threads:[~2016-01-11 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 23:51 Jeff Merkey
2015-12-14  1:24 ` Jeff Merkey
2015-12-14  3:02   ` Jeff Merkey
2016-01-11 20:40     ` Linus Torvalds
2016-01-11 20:58       ` Thomas Gleixner [this message]
2016-01-11 21:30         ` Jeff Merkey
2016-01-11 21:27       ` Jeff Merkey

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=alpine.DEB.2.11.1601112156530.3575@nanos \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.mdb@gmail.com \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --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®