All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Andi Kleen <ak@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	robert.richter@amd.com, Greg KH <greg@kroah.com>,
	Anton Blanchard <anton@au1.ibm.com>,
	linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@google.com>,
	linuxppc-dev@ozlabs.org, Ingo Molnar <mingo@redhat.com>,
	Paul Mackerras <paulus@samba.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries
Date: Fri, 18 Jan 2013 16:20:32 -0300	[thread overview]
Message-ID: <20130118192032.GB2390@ghostprotocols.net> (raw)
In-Reply-To: <20130118174654.GA12575@us.ibm.com>

Em Fri, Jan 18, 2013 at 09:46:54AM -0800, Sukadev Bhattiprolu escreveu:
> Jiri Olsa [jolsa@redhat.com] wrote:
> | Maybe it'd worth to mention, that it does not need to be just 'event',
> | but anything from /sys/bus/event_source/devices/<dev>/format directory,
> | like
> | 
> | 		The can be multiple terms like 'event=0xNNNN' specified
> | 		and separated with comma. All available terms are located
> | 		in /sys/bus/event_source/devices/<dev>/format file.
> | 
> | Please feel free to rephrase or use proper English ;-)
> | 
> | otherwise it's ok,
> | jirka
> 
> Agree.  Thanks for the review. Here is the updated patch.

Ok, I'll wait for Jiri's final acked-by, then you can resubmit the patch
series and I'll apply it to my perf/core branch.

- Arnaldo

WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Anton Blanchard <anton@au1.ibm.com>,
	robert.richter@amd.com, linuxppc-dev@ozlabs.org,
	linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@google.com>,
	Andi Kleen <ak@linux.intel.com>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries
Date: Fri, 18 Jan 2013 16:20:32 -0300	[thread overview]
Message-ID: <20130118192032.GB2390@ghostprotocols.net> (raw)
In-Reply-To: <20130118174654.GA12575@us.ibm.com>

Em Fri, Jan 18, 2013 at 09:46:54AM -0800, Sukadev Bhattiprolu escreveu:
> Jiri Olsa [jolsa@redhat.com] wrote:
> | Maybe it'd worth to mention, that it does not need to be just 'event',
> | but anything from /sys/bus/event_source/devices/<dev>/format directory,
> | like
> | 
> | 		The can be multiple terms like 'event=0xNNNN' specified
> | 		and separated with comma. All available terms are located
> | 		in /sys/bus/event_source/devices/<dev>/format file.
> | 
> | Please feel free to rephrase or use proper English ;-)
> | 
> | otherwise it's ok,
> | jirka
> 
> Agree.  Thanks for the review. Here is the updated patch.

Ok, I'll wait for Jiri's final acked-by, then you can resubmit the patch
series and I'll apply it to my perf/core branch.

- Arnaldo

  reply	other threads:[~2013-01-18 19:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  1:03 [PATCH 1/6][v3] perf/Power7: Use macros to identify perf events Sukadev Bhattiprolu
2013-01-10  1:03 ` Sukadev Bhattiprolu
2013-01-10  1:04 ` [PATCH 2/6][v3] perf: Make EVENT_ATTR global Sukadev Bhattiprolu
2013-01-10  1:04   ` Sukadev Bhattiprolu
2013-01-10  1:05 ` [PATCH 3/6][v3] perf/POWER7: Make generic event translations available in sysfs Sukadev Bhattiprolu
2013-01-10  1:05   ` Sukadev Bhattiprolu
2013-01-10  1:06 ` [PATCH 4/6][v3] perf/POWER7: Make some POWER7 events " Sukadev Bhattiprolu
2013-01-10  1:06   ` Sukadev Bhattiprolu
2013-01-10  1:06 ` [PATCH 5/6][v3] perf: Create a sysfs entry for Power event format Sukadev Bhattiprolu
2013-01-10  1:06   ` Sukadev Bhattiprolu
2013-01-10  1:07 ` [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries Sukadev Bhattiprolu
2013-01-10  1:07   ` Sukadev Bhattiprolu
2013-01-15 18:57   ` Arnaldo Carvalho de Melo
2013-01-15 18:57     ` Arnaldo Carvalho de Melo
2013-01-15 22:47     ` Greg KH
2013-01-15 22:47       ` Greg KH
2013-01-16 11:30     ` Jiri Olsa
2013-01-16 11:30       ` Jiri Olsa
2013-01-16 18:58       ` Sukadev Bhattiprolu
2013-01-16 18:58         ` Sukadev Bhattiprolu
2013-01-17 14:11         ` Jiri Olsa
2013-01-17 14:11           ` Jiri Olsa
2013-01-18 17:46           ` Sukadev Bhattiprolu
2013-01-18 17:46             ` Sukadev Bhattiprolu
2013-01-18 19:20             ` Arnaldo Carvalho de Melo [this message]
2013-01-18 19:20               ` Arnaldo Carvalho de Melo
2013-01-22 17:10             ` Jiri Olsa
2013-01-22 17:10               ` Jiri Olsa
2013-01-23  3:50 ` [PATCH 1/6][v3] perf/Power7: Use macros to identify perf events Michael Ellerman
2013-01-23  3:50   ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2013-01-10  0:06 sukadev
2013-01-10  0:06 ` [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries sukadev

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=20130118192032.GB2390@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@linux.intel.com \
    --cc=anton@au1.ibm.com \
    --cc=eranian@google.com \
    --cc=greg@kroah.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=robert.richter@amd.com \
    --cc=sukadev@linux.vnet.ibm.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 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.