[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFykGfw2ijEXPreqBqE7mpqEr7WSD1NK8FHmrqwOxZD5BQ@mail.gmail.com>
Date: Mon, 25 Jul 2016 14:45:53 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Ingo Molnar <mingo@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Jiri Olsa <jolsa@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] perf changes for v4.8
On Mon, Jul 25, 2016 at 2:21 PM, Stephen Rothwell <sfr@...b.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?
Linus
Powered by blists - more mailing lists