From: mlangsdo@redhat.com (Mark Langsdorf)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1
Date: Mon, 13 Jul 2015 11:55:54 -0500 [thread overview]
Message-ID: <55A3ED9A.6050007@redhat.com> (raw)
In-Reply-To: <20150709165944.GA19282@twins.programming.kicks-ass.net>
On 07/09/2015 11:59 AM, Peter Zijlstra wrote:
> On Thu, Jul 09, 2015 at 11:46:04AM -0500, Mark Langsdorf wrote:
>> I did a git bisect and it looks like the faulty patch is
>> d72da4a4d973d8a0a0d3c97e7cdebf287fbe3a99, "rbtree: Make lockless
>> searches non-fatal". I can't see why it causes my builds to fail,
>> but if I revert that patch and the related series, then I can
>> build the kernel and build tools/perf successfully.
>>
>> Any insight into a less intensive way of fixing my build would
>> be appreciated.
>
> This is tools/perf failing to build right? Add tip/perf/urgent, it
> appears to contain the required bits to make it go again.
>
> The /urgent branches will get to Linus 'soon' I imagine.
Thanks, that resolved it.
--Mark Langsdorf
prev parent reply other threads:[~2015-07-13 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+55aFxmm7THBsCK62esr=JCcHpn6nmReGKqPp0inUrhbkveuA@mail.gmail.com>
[not found] ` <559BCC8A.1030708@redhat.com>
2015-07-09 16:46 ` Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1 Mark Langsdorf
2015-07-09 16:59 ` Peter Zijlstra
2015-07-13 16:55 ` Mark Langsdorf [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=55A3ED9A.6050007@redhat.com \
--to=mlangsdo@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).