From: Ian Rogers <irogers@google.com>
To: Yang Jihong <yangjihong@bytedance.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
adrian.hunter@intel.com, kan.liang@linux.intel.com,
james.clark@arm.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] perf build: Specify libtraceevent dir to rpath for asan/msan build on 64-bit
Date: Mon, 13 May 2024 10:56:35 -0700 [thread overview]
Message-ID: <CAP-5=fW0EE+Wix_Z2o2DxTcOzm89hgsujt9e+MZi9GpRn1OuPA@mail.gmail.com> (raw)
In-Reply-To: <20240513074910.1660373-1-yangjihong@bytedance.com>
On Mon, May 13, 2024 at 12:49 AM Yang Jihong <yangjihong@bytedance.com> wrote:
>
> This patchset is for asan build issues. For detailed discussion, see:
> https://lore.kernel.org/all/CAP-5=fXJAu8OO_Gaw45Hx3uq6N8VQBNFhqcUy3Zm2vKT-TDSOQ@mail.gmail.com/
> https://lore.kernel.org/all/CAP-5=fXYH4JnfQH98vPRttViBfYAWGA-aoGXO7q+R_Wt8AqFSw@mail.gmail.com/
>
> Yang Jihong (2):
> perf build: Specify libtraceevent dir to rpath for asan/msan build
> perf build: Add libtraceevent lib64 to -L directory & rpath on 64-bit
Great, thanks!
Tested-by: Ian Rogers <irogers@google.com>
> tools/perf/Makefile.config | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> --
> 2.25.1
>
prev parent reply other threads:[~2024-05-13 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 7:49 [PATCH v2 0/2] perf build: Specify libtraceevent dir to rpath for asan/msan build on 64-bit Yang Jihong
2024-05-13 7:49 ` [PATCH v2 1/2] perf build: Specify libtraceevent dir to rpath for asan/msan build Yang Jihong
2024-05-13 7:49 ` [PATCH v2 2/2] perf build: Add libtraceevent lib64 to -L directory & rpath on 64-bit Yang Jihong
2024-05-13 17:56 ` Ian Rogers [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='CAP-5=fW0EE+Wix_Z2o2DxTcOzm89hgsujt9e+MZi9GpRn1OuPA@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.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 \
--cc=yangjihong@bytedance.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).