From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Leo Yan <leo.yan@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
James Clark <james.clark@linaro.org>,
amadio@gentoo.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 0/6] perf: build: Fix cross compilation
Date: Fri, 26 Jul 2024 09:37:09 -0300 [thread overview]
Message-ID: <ZqOYdX5TSk1odkCH@x1> (raw)
In-Reply-To: <ZqL7gu8AOvS1gOlq@google.com>
On Thu, Jul 25, 2024 at 06:27:30PM -0700, Namhyung Kim wrote:
> Hi Leo,
>
> On Thu, Jul 25, 2024 at 07:53:18AM +0100, Leo Yan wrote:
> > Hi Arnaldo, Namhyung,
> >
> > On 7/17/2024 9:22 AM, Leo Yan wrote:
> > > This patch series fixes cross compilation issues.
> >
> > If this series is fine for you, would you mind to pick up this series?
>
> Sure, I think we can carry this through perf-tools if Arnaldo is ok.
Well, rc1 isn't out, this has been out for a few weeks, so I think its
ok to have it for the current merge window.
- Arnaldo
prev parent reply other threads:[~2024-07-26 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 8:22 [PATCH v5 0/6] perf: build: Fix cross compilation Leo Yan
2024-07-17 8:22 ` [PATCH v5 1/6] perf: build: Setup PKG_CONFIG_LIBDIR for " Leo Yan
2024-07-17 8:22 ` [PATCH v5 2/6] perf: build: Set Python configuration " Leo Yan
2024-07-17 8:22 ` [PATCH v5 3/6] perf: build: Only link libebl.a for old libdw Leo Yan
2024-07-17 8:22 ` [PATCH v5 4/6] perf: build: Link lib 'lzma' for static build Leo Yan
2024-07-17 8:22 ` [PATCH v5 5/6] perf: build: Link lib 'zstd' " Leo Yan
2024-07-17 8:22 ` [PATCH v5 6/6] perf docs: Document cross compilation Leo Yan
2024-07-17 15:22 ` [PATCH v5 0/6] perf: build: Fix " Ian Rogers
2024-07-25 6:53 ` Leo Yan
2024-07-26 1:27 ` Namhyung Kim
2024-07-26 12:37 ` Arnaldo Carvalho de Melo [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=ZqOYdX5TSk1odkCH@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=amadio@gentoo.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--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=namhyung@kernel.org \
--cc=tmricht@linux.ibm.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.