public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Davidlohr Bueso <davidlohr@hp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Anvin <hpa@zytor.com>
Subject: Re: [GIT PULL] locking tree changes for v3.16
Date: Thu, 5 Jun 2014 10:19:15 +0200	[thread overview]
Message-ID: <20140605081915.GD4926@gmail.com> (raw)
In-Reply-To: <CA+55aFzsTqKhAOwEm+-M_ELzRFvPMYtUn8DNM9FiUMzaeZP0pw@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > I _think_ tip/locking/core is empty and you could pull that into your
> > tree without getting tons of extra weird stuff, but if you prefer a tree
> > based on your git tree I'll have to do some manual stuff but that is
> > certainly possible.
> 
> I'd actually prefer against something like the v3.15-rc8 tag, just so
> that the tree is otherwise "pristine".
> 
> > Also, this 'obviously' does not have the normal tip build coverage,
> > because I usually rely on the tip build robots to do that. But it does
> > build and run for all my local machines.
> 
> It would be great to have Davidlohr go over it too, and if possible
> have it run through the build robots. [...]

The build/boot robots found breakage and that is why its first 
iteration was removed, I didn't have fundamental objections.

Thanks,

	Ingo

  parent reply	other threads:[~2014-06-05  8:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:48 [GIT PULL] locking tree changes for v3.16 Ingo Molnar
2014-06-03 21:50 ` Davidlohr Bueso
2014-06-03 21:55   ` Andrew Morton
2014-06-03 22:02     ` Davidlohr Bueso
2014-06-03 22:53       ` Andrew Morton
2014-06-04 10:30   ` Peter Zijlstra
2014-06-04 16:17     ` Linus Torvalds
2014-06-04 17:22       ` Peter Zijlstra
2014-06-04 21:22         ` Linus Torvalds
2014-06-04 21:35           ` Thomas Gleixner
2014-06-05  1:22           ` Davidlohr Bueso
2014-06-05  8:19           ` Ingo Molnar [this message]
2014-06-05  8:22             ` Thomas Gleixner
2014-06-05  8:29               ` Ingo Molnar
2014-06-05  8:17     ` Ingo Molnar
2014-06-05  9:21       ` Peter Zijlstra
2014-06-05  9:24         ` Ingo Molnar
2014-06-05 11:11       ` Ingo Molnar
2014-06-05 11:20         ` Ingo Molnar
2014-06-05 12:27         ` Peter Zijlstra
2014-06-05 12:35           ` Ingo Molnar
2014-06-05 12:41             ` Peter Zijlstra
2014-06-05 12:47               ` Ingo Molnar
2014-06-05 12:53         ` Peter Zijlstra
2014-06-05 13:13           ` Peter Zijlstra

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=20140605081915.GD4926@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=davidlohr@hp.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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