mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, ak@linux.intel.com,
	acme@redhat.com, jolsa@redhat.com, zheng.z.yan@intel.com,
	bp@alien8.de, maria.n.dimakopoulou@gmail.com
Subject: Re: [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support
Date: Wed, 27 Nov 2013 11:23:10 +0100	[thread overview]
Message-ID: <20131127102310.GX10022@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1384275531-10892-4-git-send-email-eranian@google.com>

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@google.com>
> Signed-off-by: Maria Dimakopoulou <maria.n.dimakopoulou@gmail.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.

  reply	other threads:[~2013-11-27 10:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 16:58 [PATCH v7 0/4] perf/x86: " Stephane Eranian
2013-11-12 16:58 ` [PATCH v7 1/4] perf: add active_entry list head to struct perf_event Stephane Eranian
2013-11-27 14:07   ` [tip:perf/core] perf: Add " tip-bot for Stephane Eranian
2013-11-12 16:58 ` [PATCH v7 2/4] perf stat: add event unit and scale support Stephane Eranian
2013-11-27 14:08   ` [tip:perf/core] tools/perf/stat: Add " tip-bot for Stephane Eranian
2013-11-12 16:58 ` [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-11-27 10:23   ` Peter Zijlstra [this message]
2013-11-27 14:08   ` [tip:perf/core] perf/x86: Add " tip-bot for Stephane Eranian
2013-11-27 18:35   ` [PATCH v7 3/4] perf,x86: add " Vince Weaver
2013-11-27 18:38     ` Stephane Eranian
2013-11-27 22:03       ` Vince Weaver
2013-11-28 12:26         ` Ingo Molnar
2013-11-28 12:35           ` Stephane Eranian
2013-11-29 19:16             ` Vince Weaver
2013-11-29 20:09               ` Stephane Eranian
2013-11-29 20:31                 ` Borislav Petkov
2013-11-29 23:25                   ` Stephane Eranian
2013-11-30 16:39                     ` Vince Weaver
2013-11-12 16:58 ` [PATCH v7 4/4] perf,x86: add RAPL hrtimer support Stephane Eranian
2013-11-27 14:10   ` [tip:perf/core] perf/x86: Add " tip-bot for Stephane Eranian
2013-11-27 14:33   ` tip-bot for Stephane Eranian
2013-11-12 18:10 ` [PATCH v7 0/4] perf/x86: add Intel RAPL PMU support Andi Kleen

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=20131127102310.GX10022@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maria.n.dimakopoulou@gmail.com \
    --cc=mingo@elte.hu \
    --cc=zheng.z.yan@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

Powered by JetHome