From: Leo Yan <leo.yan@arm.com>
To: Guilherme Amadio <amadio@gentoo.org>, Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ian Rogers <irogers@google.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
linux-perf-users@vger.kernel.org,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] perf build: libtraceevent, libtracefs feature check with pkg-config
Date: Wed, 17 Jul 2024 20:47:51 +0100 [thread overview]
Message-ID: <b12aa046-b50f-4c05-b996-9f8eba0d43ea@arm.com> (raw)
In-Reply-To: <20240717174739.186988-1-amadio@gentoo.org>
On 7/17/2024 6:47 PM, Guilherme Amadio wrote:
>
> This patch series is a continuation of recent work to use pkg-config for feature
> checks for libtraceevent and libtracefs.
Tested this series for building x86_64 target and cross building aarch64 target:
Tested-by: Leo Yan <leo.yan@arm.com>
prev parent reply other threads:[~2024-07-17 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240717123147.17169873@rorschach.local.home>
2024-07-17 17:47 ` [PATCH v3 0/5] perf build: libtraceevent, libtracefs feature check with pkg-config Guilherme Amadio
2024-07-17 17:47 ` [PATCH v3 1/5] perf build: Warn if libtracefs is not found Guilherme Amadio
2024-07-17 17:47 ` [PATCH v3 2/5] tools: Make pkg-config dependency checks usable by other tools Guilherme Amadio
2024-07-17 17:47 ` [PATCH v3 3/5] tools/verification: Use pkg-config in lib_setup of Makefile.config Guilherme Amadio
2024-07-17 17:47 ` [PATCH v3 4/5] tools/rtla: " Guilherme Amadio
2024-07-17 17:47 ` [PATCH v3 5/5] tools/latency: " Guilherme Amadio
2024-07-17 17:57 ` [PATCH v3 0/5] perf build: libtraceevent, libtracefs feature check with pkg-config Steven Rostedt
2024-07-17 20:17 ` Namhyung Kim
2024-07-17 19:47 ` Leo Yan [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=b12aa046-b50f-4c05-b996-9f8eba0d43ea@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=amadio@gentoo.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).