public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail•com>
To: Jiri Olsa <jolsa@redhat•com>
Cc: "Quentin Monnet" <quentin.monnet@netronome•com>,
	"Jiri Olsa" <jolsa@kernel•org>,
	lkml <linux-kernel@vger•kernel.org>,
	netdev@vger•kernel.org, bpf@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>,
	"Toke Høiland-Jørgensen" <toke@redhat•com>,
	"Jesper Dangaard Brouer" <brouer@redhat•com>,
	"Daniel Borkmann" <daniel@iogearbox•net>,
	"Alexei Starovoitov" <alexei.starovoitov@gmail•com>,
	"Martin KaFai Lau" <kafai@fb•com>,
	"Song Liu" <songliubraving@fb•com>, "Yonghong Song" <yhs@fb•com>,
	"Andrii Nakryiko" <andriin@fb•com>
Subject: Re: [PATCH 3/3] bpftool: Allow to link libbpf dynamically
Date: Wed, 27 Nov 2019 11:24:49 -0300	[thread overview]
Message-ID: <20191127142449.GD22719@kernel.org> (raw)
In-Reply-To: <20191127141520.GJ32367@krava>

Em Wed, Nov 27, 2019 at 03:15:20PM +0100, Jiri Olsa escreveu:
> On Wed, Nov 27, 2019 at 01:38:55PM +0000, Quentin Monnet wrote:
> > 2019-11-27 10:48 UTC+0100 ~ Jiri Olsa <jolsa@kernel•org>
> > On the plus side, all build attempts from
> > tools/testing/selftests/bpf/test_bpftool_build.sh pass successfully on
> > my setup with dynamic linking from your branch.
> 
> cool, had no idea there was such test ;-)

Should be the the equivalent to 'make -C tools/perf build-test' :-)

Perhaps we should make tools/testing/selftests/perf/ link to that?

- Arnaldo

  reply	other threads:[~2019-11-27 14:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  9:48 [PATCH 0/3] perf/bpftool: Allow to link libbpf dynamically Jiri Olsa
2019-11-27  9:48 ` [PATCH 1/3] perf tools: Allow to specify libbpf install directory Jiri Olsa
2019-11-27  9:48 ` [PATCH 2/3] libbpf: Export netlink functions used by bpftool Jiri Olsa
2019-11-27  9:48 ` [PATCH 3/3] bpftool: Allow to link libbpf dynamically Jiri Olsa
2019-11-27 13:38   ` Quentin Monnet
2019-11-27 14:15     ` Jiri Olsa
2019-11-27 14:24       ` Arnaldo Carvalho de Melo [this message]
2019-11-27 14:31         ` Quentin Monnet
2019-11-27 15:48           ` Arnaldo Carvalho de Melo
2019-11-27 15:52             ` Quentin Monnet
2019-11-27 15:59               ` Arnaldo Carvalho de Melo
2019-11-27 14:29       ` Quentin Monnet
2019-11-27 16:41   ` Alexei Starovoitov
2019-11-27 16:37 ` [PATCH 0/3] perf/bpftool: " Alexei Starovoitov
2019-11-27 18:44   ` Arnaldo Carvalho de Melo
2019-11-27 20:24   ` Andrii Nakryiko
2019-11-27 21:22     ` Daniel Borkmann
2019-11-27 22:47       ` Jiri Olsa
2019-11-28  9:06   ` Toke Høiland-Jørgensen
2019-11-28 14:53 ` [PATCH bpf v2] bpftool: " Toke Høiland-Jørgensen
2019-11-28 15:32   ` Quentin Monnet
2019-11-28 15:52     ` Toke Høiland-Jørgensen
2019-11-28 16:07   ` [PATCH bpf v3] " Toke Høiland-Jørgensen
2019-11-28 17:30     ` Quentin Monnet
2019-11-29  8:12     ` Jiri Olsa
2019-11-29  8:24       ` Toke Høiland-Jørgensen
2019-11-29 10:24     ` Daniel Borkmann
2019-11-29 14:00       ` Toke Høiland-Jørgensen
2019-11-29 23:56         ` Daniel Borkmann
2019-12-02  8:59           ` Jiri Olsa
2019-12-02 17:09 ` [PATCH 0/3] perf/bpftool: " Andrii Nakryiko
2019-12-02 18:08   ` Toke Høiland-Jørgensen
2019-12-02 18:42     ` Andrii Nakryiko
2019-12-02 18:54       ` Arnaldo Carvalho de Melo
2019-12-02 19:21       ` Jiri Olsa
2019-12-02 19:54         ` Andrii Nakryiko
2019-12-02 20:02           ` 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=20191127142449.GD22719@kernel.org \
    --to=arnaldo.melo@gmail$(echo .)com \
    --cc=a.p.zijlstra@chello$(echo .)nl \
    --cc=alexander.shishkin@linux$(echo .)intel.com \
    --cc=alexei.starovoitov@gmail$(echo .)com \
    --cc=andriin@fb$(echo .)com \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=brouer@redhat$(echo .)com \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=jolsa@kernel$(echo .)org \
    --cc=jolsa@redhat$(echo .)com \
    --cc=kafai@fb$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=mingo@kernel$(echo .)org \
    --cc=mpetlan@redhat$(echo .)com \
    --cc=namhyung@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=quentin.monnet@netronome$(echo .)com \
    --cc=songliubraving@fb$(echo .)com \
    --cc=toke@redhat$(echo .)com \
    --cc=yhs@fb$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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