From: Ian Rogers <irogers@google.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Weilin Wang <weilin.wang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
John Garry <john.g.garry@oracle.com>,
Sandipan Das <sandipan.das@amd.com>
Subject: Re: [PATCH v2 2/2] perf jevents: Autogenerate empty-pmu-events.c
Date: Mon, 29 Jul 2024 12:18:34 -0700 [thread overview]
Message-ID: <CAP-5=fWS6F09aNgz9FVRrAK5ZRvSJ=8o4UAkTfsHdZVaoMi_-Q@mail.gmail.com> (raw)
In-Reply-To: <ZpXdUiNhFbqJvkZK@xsang-OptiPlex-9020>
On Mon, Jul 15, 2024 at 7:39 PM Oliver Sang <oliver.sang@intel.com> wrote:
>
> hi, Ian,
>
> thanks a lot for detail analysis! we will check further.
Hi Oliver,
I'd like to see these patches land, is there any follow up? I think
the build breakage was patches applied incorrectly so I don't think
there is any reason not to take the series.
Thanks,
Ian
next prev parent reply other threads:[~2024-07-29 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 1:30 [PATCH v2 1/2] perf jevents: Use name for special find value Ian Rogers
2024-05-25 1:30 ` [PATCH v2 2/2] perf jevents: Autogenerate empty-pmu-events.c Ian Rogers
2024-05-28 10:00 ` John Garry
2024-05-28 15:14 ` Ian Rogers
2024-05-31 8:16 ` kernel test robot
2024-05-31 16:38 ` Ian Rogers
2024-06-03 14:19 ` Oliver Sang
2024-06-03 15:46 ` Ian Rogers
2024-06-12 21:46 ` Ian Rogers
2024-06-13 3:04 ` Oliver Sang
2024-07-16 0:23 ` Ian Rogers
2024-07-16 2:39 ` Oliver Sang
2024-07-29 19:18 ` Ian Rogers [this message]
2024-07-30 1:47 ` Oliver Sang
2024-05-28 9:55 ` [PATCH v2 1/2] perf jevents: Use name for special find value John Garry
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=fWS6F09aNgz9FVRrAK5ZRvSJ=8o4UAkTfsHdZVaoMi_-Q@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=john.g.garry@oracle.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=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=sandipan.das@amd.com \
--cc=weilin.wang@intel.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 NNTP newsgroup(s).