[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9aef5f82-fa76-dbb5-59a0-47f2e85f8bda@oracle.com>
Date: Fri, 30 Jun 2023 10:35:00 +0100
From: John Garry <john.g.garry@...cle.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: acme@...nel.org, irogers@...gle.com, jolsa@...nel.org,
linux-arm-kernel@...ts.infradead.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
renyu.zj@...ux.alibaba.com, shangxiaojing@...wei.com,
zhangshaokun@...ilicon.com, qiangqing.zhang@....com,
kjain@...ux.ibm.com, kan.liang@...ux.intel.com
Subject: Re: [PATCH RFC 0/9] perf tool: sys event metric support re-write
>>
>> Based on 82fe2e45cdb0 (acme/tmp.perf/core, acme/tmp.perf-tools-next, acme/perf/core, acme/perf-tools-next) perf pmus: Check if we can encode the PMU number in perf_event_attr.type
>
> We moved to new repos from acme to perf/perf-tools and perf/perf-tools-next.
> You'd better rebase the series onto perf-tools-next (branch name is the same).
Is that in the MAINTAINERS file? I could not see it.
And I was hoping that Ian could first have a look, since this is just an
RFC.
Cheers,
John
Powered by blists - more mailing lists