From: Namhyung Kim <namhyung@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: [GIT PULL] perf-tools fixes for v6.11-rc1
Date: Tue, 23 Jul 2024 16:04:36 -0700 [thread overview]
Message-ID: <20240723230436.1050616-1-namhyung@kernel.org> (raw)
Hi Linus,
Please consider pulling the following changes in perf tools for v6.11.
Thanks,
Namhyung
The following changes since commit 7a2fb5619cc1fb53cb8784154d5ef2bd99997436:
perf trace: Fix iteration of syscall ids in syscalltbl->entries (2024-07-12 09:49:02 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tags/perf-tools-fixes-for-v6.11-2024-07-23
for you to fetch changes up to 92717bc077892d1ce60fee07aee3a33f33909b85:
perf dso: Fix build when libunwind is enabled (2024-07-17 13:17:57 -0700)
----------------------------------------------------------------
perf tools fixes for v6.11
Two fixes about building perf and other tools:
* Fix breakage in tracing tools due to pkg-config for libtrace{event,fs}
* Fix build of perf when libunwind is used
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
----------------------------------------------------------------
Guilherme Amadio (5):
perf build: Warn if libtracefs is not found
tools: Make pkg-config dependency checks usable by other tools
tools/verification: Use pkg-config in lib_setup of Makefile.config
tools/rtla: Use pkg-config in lib_setup of Makefile.config
tools/latency: Use pkg-config in lib_setup of Makefile.config
James Clark (1):
perf dso: Fix build when libunwind is enabled
tools/build/Makefile.feature | 18 ++++++++++++++++++
tools/perf/Makefile.config | 13 +++++--------
tools/perf/util/dso.c | 2 +-
tools/perf/util/dso.h | 5 +++++
tools/perf/util/unwind-libunwind-local.c | 2 +-
tools/tracing/latency/Makefile.config | 3 ++-
tools/tracing/rtla/Makefile.config | 3 ++-
tools/verification/rv/Makefile.config | 3 ++-
8 files changed, 36 insertions(+), 13 deletions(-)
next reply other threads:[~2024-07-23 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 23:04 Namhyung Kim [this message]
2024-07-24 1:21 ` [GIT PULL] perf-tools fixes for v6.11-rc1 pr-tracker-bot
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=20240723230436.1050616-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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