From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: perf: Convert event enums to #defines
Date: Wed, 28 Oct 2015 15:16:40 +0000 [thread overview]
Message-ID: <20151028151639.GD18966@arm.com> (raw)
In-Reply-To: <20151028151352.GD12239@dreric01-gentoo.localdomain>
On Wed, Oct 28, 2015 at 08:13:53AM -0700, Drew Richardson wrote:
> On Wed, Oct 28, 2015 at 08:10:14AM -0700, Drew Richardson wrote:
> > Add additional information about the ARM architected hardware events
> > to make counters self describing. This makes the hardware PMUs easier
> > to use as perf list contains possible events instead of users having
> > to refer to documentation like the ARM TRMs.
[...]
> Sorry, I need to fix my email setup/git. This is 2/2 for the patch,
> not 1/2.
Your first patch also has a second header, so it doesn't apply.
Will
next prev parent reply other threads:[~2015-10-28 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 15:07 [PATCH v6 0/2] arm: perf: Add event descriptions Drew Richardson
2015-10-28 15:08 ` [PATCH 1/2] arm: perf: Convert event enums to #defines Drew Richardson
2015-10-28 15:10 ` Drew Richardson
2015-10-28 15:13 ` Drew Richardson
2015-10-28 15:16 ` Will Deacon [this message]
2015-10-28 15:19 ` [PATCH v6 " Drew Richardson
2015-10-28 15:20 ` [PATCH v6 2/2] arm: perf: Add event descriptions Drew Richardson
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=20151028151639.GD18966@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).