public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Quentin Monnet <qmo@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Nick Terrell <terrelln@fb.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	James Clark <james.clark@linaro.org>,
	Guilherme Amadio <amadio@gentoo.org>,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 3/3] bpftool: Link zstd lib required by libelf
Date: Mon, 16 Dec 2024 18:06:36 -0300	[thread overview]
Message-ID: <Z2CWXKVj87gmWjF3@x1> (raw)
In-Reply-To: <20241216163033.GA700645@e132581.arm.com>

On Mon, Dec 16, 2024 at 04:30:33PM +0000, Leo Yan wrote:
> On Mon, Dec 16, 2024 at 11:23:29AM +0000, Quentin Monnet wrote:
> > 
> > 2024-12-15 22:12 UTC+0000 ~ Leo Yan <leo.yan@arm.com>
> > > When the feature libelf-zstd is detected, the zstd lib is required by
> > > libelf.  Link the zstd lib in this case.
> > >
> > > Signed-off-by: Leo Yan <leo.yan@arm.com>
> > > Tested-by: Namhyung Kim <namhyung@kernel.org>
> > > Acked-by: Andrii Nakryiko <andrii@kernel.org>
> > 
> > Reviewed-by: Quentin Monnet <qmo@kernel.org>
> > 
> > Thank you! And thanks for the updated commit description in your first
> > patch, looks great.
> 
> Thank you for continuous review, Quentin!

Applied locally and test building now, please holler if someone thinks
this should be processed somewhere else.

- Arnaldo

      reply	other threads:[~2024-12-16 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 22:12 [PATCH v3 0/3] bpftool: Fix the static linkage failure Leo Yan
2024-12-15 22:12 ` [PATCH v3 1/3] tools build: Add feature test for libelf with ZSTD Leo Yan
2024-12-15 22:12 ` [PATCH v3 2/3] perf: build: Minor improvement for linking libzstd Leo Yan
2024-12-15 22:12 ` [PATCH v3 3/3] bpftool: Link zstd lib required by libelf Leo Yan
2024-12-16 11:23   ` Quentin Monnet
2024-12-16 16:30     ` Leo Yan
2024-12-16 21:06       ` Arnaldo Carvalho de Melo [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=Z2CWXKVj87gmWjF3@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=amadio@gentoo.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kpsingh@kernel.org \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=namhyung@kernel.org \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=terrelln@fb.com \
    --cc=yonghong.song@linux.dev \
    /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