From: Yang Jihong <yangjihong@bytedance.com>
To: Leo Yan <leo.yan@arm.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH v3 0/3] perf: build: Minor fixes for build failures
Date: Mon, 9 Sep 2024 10:15:26 +0800 [thread overview]
Message-ID: <32df3e10-994d-4966-9f8f-e9b736140ded@bytedance.com> (raw)
In-Reply-To: <b5688d4a-9389-4998-8031-3f002302311e@arm.com>
Hello,
PING.
Are there any other issues with this patchset?
Thanks,
Yang.
On 8/7/24 15:49, Leo Yan wrote:
> On 8/7/2024 4:20 AM, Yang Jihong wrote:
>> Changes since v2:
>> - patch1: change LIBDW_VERSION to follow up the style of
>> LIBTRACEEVENT_VERSION. (by Leo's suggestion)
>> - patch2: Use a new line for the -ldl dependency and with comment,
>> synchronize tools/perf/Makefile.config. (by Leo's suggestion)
>> - patch3: include header files in alphabetical order,
>> add reviewed-by tag from Leo. (by Leo's suggestion)
>
> For this series:
>
> Reviewed-by: Leo Yan <leo.yan@arm.com>
prev parent reply other threads:[~2024-09-09 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 3:20 [PATCH v3 0/3] perf: build: Minor fixes for build failures Yang Jihong
2024-08-07 3:20 ` [PATCH v3 1/3] perf: build: Fix static compilation error when libdw is not installed Yang Jihong
2024-08-07 3:20 ` [PATCH v3 2/3] perf: build: Fix build feature-dwarf_getlocations fail for old libdw Yang Jihong
2024-08-07 7:49 ` [PATCH v3 0/3] perf: build: Minor fixes for build failures Leo Yan
2024-09-09 2:15 ` Yang Jihong [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=32df3e10-994d-4966-9f8f-e9b736140ded@bytedance.com \
--to=yangjihong@bytedance.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).