From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ben Hutchings <ben@decadent.org.uk>, Xu Yang <xu.yang_2@nxp.com>,
Ian Rogers <irogers@google.com>,
Veronika Molnarova <vmolnaro@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Michael Petlan <mpetlan@redhat.com>,
Radostin Stoyanov <rstoyano@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] perf tests pmu: Initialize all fields of test_pmu variable
Date: Fri, 30 Aug 2024 10:37:05 -0300 [thread overview]
Message-ID: <ZtHLAcgDT7S51vUg@x1> (raw)
In-Reply-To: <CAM9d7ch3wYvqKE9HANvhinnBqgtnA6suzLYrd4bkFZ-wjqdOQw@mail.gmail.com>
On Thu, Aug 29, 2024 at 08:49:05PM -0700, Namhyung Kim wrote:
> On Thu, Aug 29, 2024 at 2:09 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Being only in perf-tools-next:
> > https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/commit/?h=perf-tools-next&id=37e2a19c98bf99747ca997be876dfc13f9165e0a
> > So yeah, probably Namhyung can cherry-pick that patch (Veronika's) into
> > perf-tools for v6.11.
> > There were a few more fixes that I noticed and picked for
> > perf-tools-next that then people reported that should also be
> > cherry-picked for v6.11, Namhyung?
> Ok, I can pick this up. I think my perf lock contention fix also can
> go to perf-tools.
> What others do you want me to pick up?
Here Ben points to one:
https://lore.kernel.org/all/d94d995e476a5c014e1ce4d75d36f8667acd3316.camel@decadent.org.uk/T/#u
Which I think its this one:
commit 2518e13275ab9ea6b2540f828cf78b0280991f85
Author: Xu Yang <xu.yang_2@nxp.com>
Date: Mon Aug 19 10:34:03 2024 +0800
perf python: Fix the build on 32-bit arm by including missing "util/sample.h"
There is also this one:
commit 6236ebe07131a7746d870f1d8eb3637a8df13e70
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Mon Aug 19 16:46:29 2024 -0300
perf daemon: Fix the build on more 32-bit architectures
The previous attempt fixed the build on debian:experimental-x-mipsel,
but when building on a larger set of containers I noticed it broke the
build on some other 32-bit architectures such as:
42 7.87 ubuntu:18.04-x-arm : FAIL gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)
builtin-daemon.c: In function 'cmd_session_list':
builtin-daemon.c:692:16: error: format '%llu' expects argument of type 'long long unsigned int', but argument 4 has type 'long int' [-Werror=format=]
- Arnaldo
prev parent reply other threads:[~2024-08-30 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 13:03 [PATCH 1/1] perf tests pmu: Initialize all fields of test_pmu variable Arnaldo Carvalho de Melo
2024-08-12 14:05 ` Veronika Molnarova
2024-08-29 20:17 ` Ian Rogers
2024-08-29 21:09 ` Arnaldo Carvalho de Melo
2024-08-30 3:49 ` Namhyung Kim
2024-08-30 13: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=ZtHLAcgDT7S51vUg@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ben@decadent.org.uk \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=rstoyano@redhat.com \
--cc=vmolnaro@redhat.com \
--cc=xu.yang_2@nxp.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