From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH 0/3] perf/libperf move
Date: Fri, 6 Dec 2019 11:21:54 -0300 [thread overview]
Message-ID: <20191206142154.GA30698@kernel.org> (raw)
In-Reply-To: <20191206135513.31586-1-jolsa@kernel.org>
Em Fri, Dec 06, 2019 at 02:55:10PM +0100, Jiri Olsa escreveu:
> NOTE 'make perf-targz-src-pkg' works nicely with this change,
> but is currently failing because of recent bpf changes, I have
> a fix for that and will send it shortly
By any means it is one of:
"libbpf: Fix up generation of bpf_helper_defs.h"
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=1fd450f99272
And:
"libbpf: Fix sym->st_value print on 32-bit arches"
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7c3977d1e804
?
I've been cherry-picking this to have my build-test and container builds
for some time waiting for those to get upstream.
- Arnaldo
next prev parent reply other threads:[~2019-12-06 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 13:55 [PATCH 0/3] perf/libperf move Jiri Olsa
2019-12-06 13:55 ` [PATCH 1/3] libperf: Move libperf under tools/lib/perf Jiri Olsa
2019-12-06 14:27 ` Arnaldo Carvalho de Melo
2019-12-06 15:07 ` Jiri Olsa
2019-12-06 15:33 ` Arnaldo Carvalho de Melo
2019-12-06 15:38 ` Jiri Olsa
2019-12-06 13:55 ` [PATCH 2/3] libperf: Additional fixes Jiri Olsa
2019-12-06 13:55 ` [PATCH 3/3] libperf: Add man pages Jiri Olsa
2019-12-06 14:21 ` Arnaldo Carvalho de Melo [this message]
2019-12-06 14:34 ` [PATCH 0/3] perf/libperf move Jiri Olsa
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=20191206142154.GA30698@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.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