From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: perf amd: PERF_MEM_LVLNUM_CXL -> PERF_MEM_LVLNUM_EXTN_MEM
Date: Wed, 26 Oct 2022 19:22:37 +0530 [thread overview]
Message-ID: <2ba741c1-ad66-c3a8-3c73-ad3819da3a27@amd.com> (raw)
In-Reply-To: <Y1k44x5PkAFNRnWo@kernel.org>
On 26-Oct-22 7:10 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Oct 26, 2022 at 11:16:24AM +0530, Ravi Bangoria escreveu:
>> Arnaldo,
>>
>> On 26-Oct-22 1:25 AM, Arnaldo Carvalho de Melo wrote:
>>> Ravi,
>>>
>>> I'm updating the tools header copies and noticed that a previous
>>> sync brought PERF_MEM_LVLNUM_CXL but now this got renamed to
>>> PERF_MEM_LVLNUM_EXTN_MEM, so I had to add this change to the sync of
>>> tools/uapi/linux/perf_event.h, please ack.
>>
>> Kernel header needs to be fixed as discussed here:
>> https://lore.kernel.org/lkml/f6268268-b4e9-9ed6-0453-65792644d953@amd.com
Peter, can you please pick up this patch.
>
> Gotcha, will leave the tools/ copy with CXL then.
>
> - Arnaldo
prev parent reply other threads:[~2022-10-26 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:55 perf amd: PERF_MEM_LVLNUM_CXL -> PERF_MEM_LVLNUM_EXTN_MEM Arnaldo Carvalho de Melo
2022-10-26 5:46 ` Ravi Bangoria
2022-10-26 13:40 ` Arnaldo Carvalho de Melo
2022-10-26 13:52 ` Ravi Bangoria [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=2ba741c1-ad66-c3a8-3c73-ad3819da3a27@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).