From: Andi Kleen <ak@linux.intel.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel <Linux-kernel@vger.kernel.org>,
"Liang, Kan" <kan.liang@intel.com>,
yao.jin@intel.com, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH] perf vendor events: Update Skylake client events to v50
Date: Sun, 15 Nov 2020 05:35:58 -0800 [thread overview]
Message-ID: <20201115133558.GN894261@tassilo.jf.intel.com> (raw)
In-Reply-To: <38be0597-7f93-0aa1-b4c5-3c7f23b74f13@linux.intel.com>
> Can I get ACK for this patch?
>
> It's mainly for fixing the perf-test issue and MEM_Parallel_Reads issue.
Acked-by: Andi Kleen <ak@linux.intel.com>
The JSON updates should be imho just merged automatically. Not much
point in doing code review on them. If there's a problem it has
to be fixed JSON upstream anyways.
-Andi
next prev parent reply other threads:[~2020-11-15 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 1:51 [PATCH] perf vendor events: Update Skylake client events to v50 Jin Yao
2020-11-06 3:00 ` Namhyung Kim
2020-11-06 3:11 ` Jin, Yao
2020-11-06 4:21 ` Namhyung Kim
2020-11-13 8:12 ` Jin, Yao
2020-11-15 13:35 ` Andi Kleen [this message]
[not found] ` <CAP-5=fW-9oj4PK=hBmvrCqfzLnoqTe502FRb74Jwqpo+3KoJKw@mail.gmail.com>
2020-11-16 8:07 ` Jin, Yao
2020-11-16 14:53 ` Andi Kleen
2020-11-16 17:05 ` Arnaldo Carvalho de Melo
[not found] ` <CAP-5=fXJCqB6sN+f-eRSwc+Za3Yri+QWMpg_G7xfz=i-cTBH3A@mail.gmail.com>
2020-11-16 19:24 ` Arnaldo Carvalho de Melo
2020-11-16 21:24 ` Andi Kleen
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=20201115133558.GN894261@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.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).