linux-kernel - Re: [PATCH 03/10] x86, perf: Add Top Down events to Intel Core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160512081019.GC20497@gmail.com>
Date:	Thu, 12 May 2016 10:10:19 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	acme@...nel.org, peterz@...radead.org, jolsa@...nel.org,
	linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 03/10] x86, perf: Add Top Down events to Intel Core

* Andi Kleen <andi@...stfloor.org> wrote:

>  Subject: Re: [PATCH 03/10] x86, perf: Add Top Down events to Intel Core

>  arch/x86/events/intel/core.c | 50 ++++++++++++++++++++++++++++++++++++++++++++

You consistently mis-spell patches to the x86 perf code and for large series this 
adds unnecessary maintainer work.

Use 'perf/x86:' for patches that affect all PMU using x86 CPUs, and 
'perf/x86/intel:' for patches that affect only Intel CPUs.

Generally a 'git log arch/x86/events/<file>.c' will tell you what pattern to use.

This applies to most of the other patches of yours in this series as well, please 
fix it - and use this consistently for future patches as well.

Thanks,

	Ingo