linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: linux-doc@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Cody P Schafer <cody@linux.vnet.ibm.com>,
	Michael Ellerman <michael@ellerman.id.au>,
	Runzhen Wang <runzhen@linux.vnet.ibm.com>,
	Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: rob@landley.net, Linux PPC <linuxppc-dev@lists.ozlabs.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: [PATCH 0/2] perf: add documentation for sysfs interfaces
Date: Wed,  5 Mar 2014 16:44:13 -0800	[thread overview]
Message-ID: <1394066658-16766-1-git-send-email-cody@linux.vnet.ibm.com> (raw)

Documents <pmu>/event/<event>{,.scale,.units} and then removes the redundant
POWER docs.

Slightly restricts <event> names to avoid API funkyness when we add new
<event>.????? files ('.' forbidden in event names).

The contact is currently lkml, it would be very useful to have a perf
development list to put here instead (acme, feel like making one?).

--

Cody P Schafer (2):
  perf Documentation: sysfs events/ interfaces
  perf Documentation: remove duplicated docs for powerpc cpu specific
    events

 .../testing/sysfs-bus-event_source-devices-events  | 92 +++++++++++-----------
 1 file changed, 47 insertions(+), 45 deletions(-)

-- 
1.9.0

             reply	other threads:[~2014-03-06  0:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  0:44 Cody P Schafer [this message]
2014-03-06  0:44 ` [PATCH 1/2] perf Documentation: sysfs events/ interfaces Cody P Schafer
2014-03-06  0:44 ` [PATCH 2/2] perf Documentation: remove duplicated docs for powerpc cpu specific events Cody P Schafer

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=1394066658-16766-1-git-send-email-cody@linux.vnet.ibm.com \
    --to=cody@linux.vnet.ibm.com \
    --cc=acme@ghostprotocols.net \
    --cc=acme@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=rob@landley.net \
    --cc=runzhen@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).