From: nleeder@codeaurora.org (Leeder, Neil)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] soc: qcom: add l2 cache perf events driver
Date: Fri, 28 Oct 2016 14:17:43 -0400 [thread overview]
Message-ID: <a0851e78-dbc5-0f1b-476a-e14561f58e2b@codeaurora.org> (raw)
In-Reply-To: <20161028160213.GH1076@arm.com>
On 10/28/2016 12:02 PM, Will Deacon wrote:
> On Tue, Oct 04, 2016 at 12:25:54PM -0400, Neil Leeder wrote:
>> Thanks Mark. I'll move it, rebase on 4.9-rc1 and run perf fuzzer.
>
> Did the fuzzer explode, or do you have a new version you can post?
>
> Will
Hi Will,
I was delayed by some logistical problems, but the fuzzer ran fine and I
will post the updated patch shortly - sorry for the delay.
Neil
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2016-10-28 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 21:12 [PATCH v6] soc: qcom: add l2 cache perf events driver Neil Leeder
2016-10-04 14:35 ` Neil Leeder
2016-10-04 15:53 ` Mark Rutland
2016-10-04 16:25 ` Neil Leeder
2016-10-28 16:02 ` Will Deacon
2016-10-28 18:17 ` Leeder, Neil [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=a0851e78-dbc5-0f1b-476a-e14561f58e2b@codeaurora.org \
--to=nleeder@codeaurora.org \
--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).