From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: commit d72da4a4d973 (rbtree: Make lockless searches non-fatal) breaks perf build
Date: Mon, 6 Jul 2015 09:57:40 +0200 [thread overview]
Message-ID: <20150706075740.GA397@x4> (raw)
In-Reply-To: <20150706075320.GB11707@gmail.com>
On 2015.07.06 at 09:53 +0200, Ingo Molnar wrote:
>
> * Markus Trippelsdorf <markus@trippelsdorf.de> wrote:
>
> > Since:
> > commit d72da4a4d973d8a0a0d3c97e7cdebf287fbe3a99
> > Author: Peter Zijlstra <peterz@infradead.org>
> > Date: Wed May 27 11:09:36 2015 +0930
> >
> > rbtree: Make lockless searches non-fatal
> >
> > perf doesn't build anymore:
>
> Yeah, can you confirm that the latest perf/urgent fixes this:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/urgent
Yes, it does. Thanks.
--
Markus
prev parent reply other threads:[~2015-07-06 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 18:09 commit d72da4a4d973 (rbtree: Make lockless searches non-fatal) breaks perf build Markus Trippelsdorf
2015-07-06 7:53 ` Ingo Molnar
2015-07-06 7:57 ` Markus Trippelsdorf [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=20150706075740.GA397@x4 \
--to=markus@trippelsdorf.de \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
/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