From: jan.glauber@caviumnetworks.com (Jan Glauber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] arm64: perf: Broadcom Vulcan PMU support
Date: Mon, 11 Apr 2016 17:34:12 +0200 [thread overview]
Message-ID: <20160411153412.GA3120@hardcore> (raw)
In-Reply-To: <1460379741-1181-1-git-send-email-ashoks@broadcom.com>
Hi Ashok,
I've tested and reviewed the previous version, it works fine on
ThunderX and the pmceid changes look good to me.
Jan
prev parent reply other threads:[~2016-04-11 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 13:02 [PATCH v4 0/6] arm64: perf: Broadcom Vulcan PMU support Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 1/6] Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding Ashok Kumar
2016-04-13 14:33 ` Rob Herring
2016-04-11 13:02 ` [PATCH v4 2/6] arm64: dts: Add Broadcom Vulcan PMU in dts Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 3/6] arm64/perf: Changed events naming as per ARM ARM Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 4/6] arm64/perf: Define complete ARMv8 recommended implementation defined events Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 5/6] arm64/perf: Filter common events based on PMCEIDn_EL0 Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 6/6] arm64/perf: Add Broadcom Vulcan PMU support Ashok Kumar
2016-04-11 15:34 ` Jan Glauber [this message]
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=20160411153412.GA3120@hardcore \
--to=jan.glauber@caviumnetworks.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).