From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers/perf: arm_pmu: fix legacy affinity-less DT support
Date: Tue, 9 Aug 2016 17:52:16 +0100 [thread overview]
Message-ID: <20160809165216.GO27508@arm.com> (raw)
In-Reply-To: <20160809164839.GN27508@arm.com>
On Tue, Aug 09, 2016 at 05:48:39PM +0100, Will Deacon wrote:
> On Tue, Aug 09, 2016 at 04:51:07PM +0100, Mark Rutland wrote:
> For now, I think I'll stick with Marc's patch (that somehow slipped through
> the woodwork), but maybe we should consider removing the SPI/PPI sanity
> checking altogether. At some point we have to rely on the DT being correct,
> and I don't think we do anything disastrout if there is a mismatch in
^^^^^
Oh dear, mind on other things.
Will
prev parent reply other threads:[~2016-08-09 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 15:51 [PATCH] drivers/perf: arm_pmu: fix legacy affinity-less DT support Mark Rutland
2016-08-09 16:48 ` Will Deacon
2016-08-09 16:51 ` Mark Rutland
2016-08-09 16:52 ` Will Deacon [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=20160809165216.GO27508@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).