From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
kan.liang@linux.intel.com, adrian.hunter@intel.com,
peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] perf jevents: Don't stop at the first matched pmu when searching a events table
Date: Mon, 30 Sep 2024 14:47:16 -0700 [thread overview]
Message-ID: <ZvscZEx5lEl6M7S8@google.com> (raw)
In-Reply-To: <CAP-5=fXk8QJjP7iDsSrS5GZz-uHYheeLg2DHCWHjD5z+jZk+9A@mail.gmail.com>
On Mon, Sep 30, 2024 at 01:30:03PM -0700, Ian Rogers wrote:
> On Mon, Sep 30, 2024 at 1:22 PM Namhyung Kim <namhyung@kernel.org> wrote:
> > I'm seeing this build failure after applying this.
> >
> > TEST pmu-events/empty-pmu-events.log
> > --- pmu-events/empty-pmu-events.c 2024-09-26 10:27:15.600055460 -0700
> > +++ pmu-events/test-empty-pmu-events.c 2024-09-30 13:20:34.631357001 -0700
> > @@ -380,7 +380,7 @@
> > continue;
> >
> > ret = pmu_events_table__for_each_event_pmu(table, table_pmu, fn, data);
> > - if (pmu || ret)
> > + if (ret)
> > return ret;
> > }
> > return 0;
> > make[3]: *** [pmu-events/Build:42: pmu-events/empty-pmu-events.log] Error 1
> > make[3]: *** Deleting file 'pmu-events/empty-pmu-events.log'
> > make[2]: *** [Makefile.perf:765: pmu-events/pmu-events-in.o] Error 2
> > make[2]: *** Waiting for unfinished jobs....
>
> Need to copy pmu-events/test-empty-pmu-events.c to
> pmu-events/empty-pmu-events.c, do you need the patch resent with this
> done?
Yes please!
Thanks
Namhyung
prev parent reply other threads:[~2024-09-30 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:29 [PATCH] perf jevents: Don't stop at the first matched pmu when searching a events table kan.liang
2024-07-16 16:30 ` Ian Rogers
2024-07-31 13:30 ` Arnaldo Carvalho de Melo
2024-09-26 21:34 ` Ian Rogers
2024-09-30 20:22 ` Namhyung Kim
2024-09-30 20:30 ` Ian Rogers
2024-09-30 21:47 ` Namhyung Kim [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=ZvscZEx5lEl6M7S8@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oliver.sang@intel.com \
--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