From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com, irogers@google.com
Subject: Re: [PATCH 0/6] perf events update for CascadeLake server and SkyLake server
Date: Wed, 11 Aug 2021 08:28:15 +0800 [thread overview]
Message-ID: <8cfa516c-af3c-49d8-90ad-1e922567a24e@linux.intel.com> (raw)
In-Reply-To: <YRLAWhHWX3oa0iyt@kernel.org>
Hi Arnaldo,
On 8/11/2021 2:07 AM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Aug 10, 2021 at 10:05:02AM +0800, Jin Yao escreveu:
>> - Update JSON core/uncore events and metrics for CascadeLake Server.
>> - Update JSON core/uncore events and metrics for SkyLake Server.
>>
>> The patch series can be found at (in case broken by mailing system potentially):
>> https://github.com/yaoj/perf-clx-events.git
>> branch: perf/core
> Hey, can you keep just one repository and then create branches?
>
Oh, yes, creating too many repos. :(
I will keep just one repo and create branches for future event updates.
Thanks
Jin Yao
prev parent reply other threads:[~2021-08-11 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 2:05 [PATCH 0/6] perf events update for CascadeLake server and SkyLake server Jin Yao
2021-08-10 2:05 ` [PATCH 2/6] perf vendor events intel: Update uncore event list for CascadeLake Server Jin Yao
2021-08-10 2:05 ` [PATCH 3/6] perf vendor events: Update metrics " Jin Yao
2021-08-10 2:05 ` [PATCH 5/6] perf vendor events intel: Update uncore event list for SkyLake Server Jin Yao
2021-08-10 2:05 ` [PATCH 6/6] perf vendor events: Update metrics " Jin Yao
2021-08-10 18:07 ` [PATCH 0/6] perf events update for CascadeLake server and SkyLake server Arnaldo Carvalho de Melo
2021-08-10 18:21 ` Arnaldo Carvalho de Melo
2021-08-11 0:28 ` Jin, Yao [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=8cfa516c-af3c-49d8-90ad-1e922567a24e@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@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).