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: Tue, 26 Jul 2016 08:45:51 +0200 [thread overview]
Message-ID: <20160726064551.GA26401@gmail.com> (raw)
In-Reply-To: <20160726075324.0aa6c782@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > That is why I sent this without mentioning the conflict. Is there any other
> > > complication that I missed?
> >
> > Actually, the perf tree on its own was enough to trigger the build problem,
> > the luto-next tree was just what initially triggered the build failure in
> > linux-next (I guess there is some missing dependency). After the build failed,
> > I started including the perf tree directly before the tip tree and the build
> > would fail when I merged that ...
>
> Now that this is fixed and merged into the tip tree, I have removed the perf
> tree from linux-next.
Ok, thanks - and sorry about this - I'll get the tooling fixes to Linus ASAP.
Thanks,
Ingo
prev parent reply other threads:[~2016-07-26 6:45 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
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 [this message]
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=20160726064551.GA26401@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox