[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200925183614.czoqgq2kcttzfm2g@two.firstfloor.org>
Date: Fri, 25 Sep 2020 11:36:15 -0700
From: Andi Kleen <andi@...stfloor.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: "Jin, Yao" <yao.jin@...ux.intel.com>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
Jiri Olsa <jolsa@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>,
Kan Liang <kan.liang@...el.com>,
Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to
v1.08
> 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
Powered by blists - more mailing lists