All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>, X86 ML <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT PULL] x86/entry changes for 3.20, round 1
Date: Thu, 15 Jan 2015 11:37:54 +0100	[thread overview]
Message-ID: <20150115103754.GC1698@gmail.com> (raw)
In-Reply-To: <20150115092740.GY9719@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> On Wed, Jan 14, 2015 at 05:59:26PM -0800, Andy Lutomirski wrote:
> > Hi Ingo and Thomas,
> > 
> > At Linus' suggestion, I'm trying out some maintainerish stuff for x86
> > entry code.  Please consider pulling to an appropriate branch *after
> > Paul sends his RCU pull request*, only if 734d16801349 is included in
> > that pull request.  If this goes well, maybe I'll submit a MAINTAINERS
> > patch, too.
> > 
> > IMPORTANT: This is based on an RCU change that you don't have yet.  I
> > think that Paul is planning on sending a pull request with that change
> > fairly soon.  The code in here would compile without that fix, but it
> > would introduce a nasty regression, so, to avoid breaking bisection, I
> > based this off of the relevant change in Paul's tree.  (It's the very
> > first change for 3.20 in his current queue.)
> 
> Yep, should happen by early next week, if it survives this weekend's
> testing.  ;-)

Ok, I'll first wait for that pull request to arrive then.

Thanks,

	Ingo

  reply	other threads:[~2015-01-15 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  1:59 [GIT PULL] x86/entry changes for 3.20, round 1 Andy Lutomirski
2015-01-15  9:27 ` Paul E. McKenney
2015-01-15 10:37   ` Ingo Molnar [this message]
2015-01-28 14:38 ` Ingo Molnar

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=20150115103754.GC1698@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.