From: Andi Kleen <andi@firstfloor.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Jin, Yao" <yao.jin@linux.intel.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Kan Liang <kan.liang@intel.com>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08
Date: Fri, 25 Sep 2020 11:36:15 -0700 [thread overview]
Message-ID: <20200925183614.czoqgq2kcttzfm2g@two.firstfloor.org> (raw)
In-Reply-To: <20200925180527.GA2883319@kernel.org>
> Thanks, it now works, but then... You forgot to add the Cc: entries for
> all the people in your actual e-mail Cc: list, and also the
> Reviewed-by: from Andy, I had to do it all manually, so when I applied
> your attachments with 'git am' I needed to go on and manually collect
> all the Cc, Reviewed-by and Acked-by tags.
For the event updates we should just use git pulls in my opinion.
They are just too large for the normal review procedures, and usually
don't really benefit much from community review anyways because they
are essentially hardware documentation.
Should just name intel / amd / etc. event list maintainers and you
could accept pulls from them.
-Andi
next prev parent reply other threads:[~2020-09-25 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 3:19 [PATCH v2 0/2] perf: Update CascadelakeX and SkylakeX events list Jin Yao
2020-09-22 19:22 ` Andi Kleen
[not found] ` <20200922031918.3723-2-yao.jin@linux.intel.com>
2020-09-22 19:42 ` [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08 Arnaldo Carvalho de Melo
[not found] ` <4db737f2-0705-5183-6971-9031acfd123b@linux.intel.com>
2020-09-23 21:04 ` Ian Rogers
2020-09-25 18:05 ` Arnaldo Carvalho de Melo
2020-09-25 18:36 ` Andi Kleen [this message]
2020-09-25 19:21 ` Arnaldo Carvalho de Melo
2020-09-25 19:43 ` Ian Rogers
2020-09-25 20:23 ` Konstantin Ryabitsev
2020-10-09 3:45 ` Jin, Yao
2020-09-28 11:47 ` Arnaldo Carvalho de Melo
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=20200925183614.czoqgq2kcttzfm2g@two.firstfloor.org \
--to=andi@firstfloor.org \
--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=konstantin@linuxfoundation.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.