All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Clark Williams <williams@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH 0/2] LIBBPF_DYNAMIC=1 fixes
Date: Fri, 19 Sep 2025 14:58:32 -0700	[thread overview]
Message-ID: <aM3SCGOXZsP3GZal@google.com> (raw)
In-Reply-To: <20250919210654.317656-1-acme@kernel.org>

On Fri, Sep 19, 2025 at 06:06:52PM -0300, Arnaldo Carvalho de Melo wrote:
> Hi,
> 
> 	Please take a look, noticed after processing a patch from Ian
> for another such issue, on a hurry now, haven't checked when that
> emit_string was introduced.
> 
> - Arnaldo
> 
> Arnaldo Carvalho de Melo (2):
>   perf bpf: Move the LIBBPF_CURRENT_VERSION_GEQ macro to bpf-utils.h
>   perf bpf: Check libbpf version to use
>     btf_dump_type_data_opts.emit_strings

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung

> 
>  tools/perf/util/bpf-event.c  | 2 ++
>  tools/perf/util/bpf-filter.c | 5 +----
>  tools/perf/util/bpf-utils.h  | 5 +++++
>  3 files changed, 8 insertions(+), 4 deletions(-)
> 
> -- 
> 2.51.0
> 

  parent reply	other threads:[~2025-09-19 21:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 21:06 [PATCH 0/2] LIBBPF_DYNAMIC=1 fixes Arnaldo Carvalho de Melo
2025-09-19 21:06 ` [PATCH 1/2] perf bpf: Move the LIBBPF_CURRENT_VERSION_GEQ macro to bpf-utils.h Arnaldo Carvalho de Melo
2025-09-19 22:04   ` Ian Rogers
2025-09-19 21:06 ` [PATCH 2/2] perf bpf: Check libbpf version to use btf_dump_type_data_opts.emit_strings Arnaldo Carvalho de Melo
2025-09-19 22:03   ` Ian Rogers
2025-09-19 21:58 ` Namhyung Kim [this message]
2025-09-19 22:10   ` [PATCH 0/2] LIBBPF_DYNAMIC=1 fixes Ian Rogers
2025-09-30 20:10     ` Ian Rogers
2025-10-01 13:34       ` Arnaldo Carvalho de Melo

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=aM3SCGOXZsP3GZal@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=andrii@kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=williams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.