All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Feng Tang <feng.tang@intel.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf, x86: Enabled PEBS event to be exported in a raw format
Date: Fri, 29 Jun 2012 14:49:08 +0200	[thread overview]
Message-ID: <20120629124908.GB32637@gmail.com> (raw)
In-Reply-To: <20120628182030.GR4152@tassilo.jf.intel.com>


* Andi Kleen <ak@linux.intel.com> wrote:

> > Not without a useful userspace part. 
> 
> http://permalink.gmane.org/gmane.linux.kernel/1319962
> 
> > Preferably not a script.
> 
> You don't need to prefer it.

Kernel development 101, Chapter 1.:

  " If you want your patches to be applied by the maintainer 
    then you'll have to address the maintainer's review 
    requests. "

Thanks,

	Ingo

  parent reply	other threads:[~2012-06-29 12:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 16:00 [PATCH] perf, x86: Enabled PEBS event to be exported in a raw format Feng Tang
2012-06-28 16:12 ` Peter Zijlstra
2012-06-28 16:15   ` Stephane Eranian
2012-06-28 16:19     ` Peter Zijlstra
2012-06-28 16:27       ` Stephane Eranian
2012-06-28 16:29         ` Peter Zijlstra
2012-06-28 18:26         ` Andi Kleen
2012-06-28 18:20   ` Andi Kleen
2012-06-28 20:51     ` Peter Zijlstra
2012-06-29  1:32       ` Feng Tang
2012-06-29  3:35         ` Andi Kleen
2012-06-29 12:49     ` Ingo Molnar [this message]
2012-07-03  7:36 ` Michael Ellerman
2012-07-03  9:15   ` Peter Zijlstra
2012-07-04  8:07     ` Michael Ellerman
2012-07-04  9:13       ` Peter Zijlstra
2012-07-05 15:57         ` Stephane Eranian
2012-07-07  7:27           ` Michael Ellerman

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=20120629124908.GB32637@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    /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.