All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Jiri Olsa <jolsa@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] perf changes for v4.8
Date: Mon, 25 Jul 2016 17:35:36 +0200	[thread overview]
Message-ID: <20160725153536.GA5715@gmail.com> (raw)
In-Reply-To: <20160725151520.GA5030@gmail.com>


* Ingo Molnar <mingo@kernel.org> wrote:

> 
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > Hi Ingo,
> > 
> > On Mon, 25 Jul 2016 10:28:38 +0200 Ingo Molnar <mingo@kernel.org> wrote:
> > >
> > >       tools: Copy the bitops files accessed from the kernel and check for drift
> > 
> > I think this has some needs some fixes for build breakage in linux-next ...
> 
> Only if combined with a single pending change from the luto-next tree, right?

... which commits come through the x86 tree, so there's no way for Linus to be 
exposed to that, right?

That is why I sent this without mentioning the conflict. Is there any other 
complication that I missed?

Thanks,

	Ingo

  reply	other threads:[~2016-07-25 15:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  8:28 [GIT PULL] perf changes for v4.8 Ingo Molnar
2016-07-25 13:53 ` Stephen Rothwell
2016-07-25 14:53   ` Arnaldo Carvalho de Melo
2016-07-25 15:15   ` Ingo Molnar
2016-07-25 15:35     ` Ingo Molnar [this message]
2016-07-25 21:21       ` Stephen Rothwell
2016-07-25 21:45         ` Linus Torvalds
2016-07-25 21:59           ` Stephen Rothwell
2016-07-26  6:38             ` Ingo Molnar
2016-07-26 21:46               ` Stephen Rothwell
2016-07-25 21:53         ` Stephen Rothwell
2016-07-26  6:45           ` 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=20160725153536.GA5715@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 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.