From: Ingo Molnar <mingo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <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:38:17 +0200 [thread overview]
Message-ID: <20160726063817.GA17368@gmail.com> (raw)
In-Reply-To: <20160726075903.18bcef41@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Linus,
>
> On Mon, 25 Jul 2016 14:45:53 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > On Mon, Jul 25, 2016 at 2:21 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > 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 ...
> >
> > Ugh. It's merged in my tree now, because I thought it was ok. Can
> > somebody point me to the fix?
>
> I only affects cross building of the objtool and vdso2c tools (which is
> how I work). The latest version of the perf/core branch in the tip
> tree now has all the fixes, so I assume that Ingo will send another
> pull request.
Yes, I'll send this ASAP.
> Unfortunately, that means that your tree is broken for me this
> morning ... but I will cope, I guess.
That's weird, I pushed out the fix from Arnaldo yesterday (about 8 hours ago)
which should merge fine with Linus's tree and make your tooling combination work.
Thanks,
Ingo
next prev parent reply other threads:[~2016-07-26 6:38 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 [this message]
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=20160726063817.GA17368@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.