linux-kernel - Re: [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support

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: <20131127102310.GX10022@twins.programming.kicks-ass.net>
Date:	Wed, 27 Nov 2013 11:23:10 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, ak@...ux.intel.com,
	acme@...hat.com, jolsa@...hat.com, zheng.z.yan@...el.com,
	bp@...en8.de, maria.n.dimakopoulou@...il.com
Subject: Re: [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support

On Tue, Nov 12, 2013 at 05:58:50PM +0100, Stephane Eranian wrote:
> Sampling is not supported by the RAPL PMU. There is no
> privilege level filtering either.
> 
> Signed-off-by: Stephane Eranian <eranian@...gle.com>
> Signed-off-by: Maria Dimakopoulou <maria.n.dimakopoulou@...il.com>

So the merge window closed and we're starting to merge new bits for the
next cycle.

Ingo fell over the double SoB here; Maria didn't actually send me this
patch, so the SoB seems awkward at best.

Sob only comes from being the primary author or from collecting it in an
aggregate work and passing it on.

I know people often use this double sob for co-authorship (even on
single line patches), but its not supported by the rules as outlined in
Documentation/SubmittingPatches.

So Ingo changed it to a Reviewed-by tag if that's fine with you -
further credits should be expressed either as split-out patches that
track authorship, or additional credits in the source code.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/