From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] [4.0] arm/arm64: Do not group hardware events from different PMUs
Date: Tue, 24 Mar 2015 15:54:08 +0000 [thread overview]
Message-ID: <1427212448.3145.22.camel@arm.com> (raw)
In-Reply-To: <1426616100-31628-1-git-send-email-suzuki.poulose@arm.com>
On Tue, 2015-03-17 at 18:14 +0000, Suzuki K. Poulose wrote:
> Similar fixes are required in ARM-CCN PMU driver and is not straight forward
> as these changes.
I'll have a look at this.
Pawel
prev parent reply other threads:[~2015-03-24 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 18:14 [PATCHv2 0/3] [4.0] arm/arm64: Do not group hardware events from different PMUs Suzuki K. Poulose
2015-03-17 18:14 ` [PATCH 1/3] arm/pmu: Reject groups spanning multiple hardware PMUs Suzuki K. Poulose
2015-03-17 18:14 ` [PATCH 2/3] arm64/pmu: Reject groups spanning multiple HW PMUs Suzuki K. Poulose
2015-03-17 18:15 ` [PATCH 3/3] arm-cci: " Suzuki K. Poulose
2015-03-18 17:18 ` [PATCHv2 0/3] [4.0] arm/arm64: Do not group hardware events from different PMUs Peter Zijlstra
2015-03-19 17:14 ` Mark Rutland
2015-03-24 15:54 ` Pawel Moll [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=1427212448.3145.22.camel@arm.com \
--to=pawel.moll@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).