From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm64: Add workaround for Cavium erratum 27456
Date: Wed, 24 Feb 2016 14:07:14 +0000 [thread overview]
Message-ID: <56CDB912.6000300@arm.com> (raw)
In-Reply-To: <20160224134016.GH28310@arm.com>
On 24/02/16 13:40, Will Deacon wrote:
[...]
> (and Catalin, if you pick this up, watch out for the conflicts in
> cpufeature.h)
Yup, that one is about to become a minefield (ARM64_HAS_NO_HW_PREFETCH,
ARM64_HAS_UAO, ARM64_ALT_PAN_NOT_UAO and ARM64_HAS_VIRT_HOST_EXTN are
already happily clashing into -next). But hey, the more the merrier! ;-)
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-02-24 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:08 [PATCH v3] arm64: Add workaround for Cavium erratum 27456 David Daney
2016-02-24 13:40 ` Will Deacon
2016-02-24 14:07 ` Marc Zyngier [this message]
2016-02-24 18:03 ` David Daney
2016-02-24 18:06 ` Will Deacon
2016-02-24 18:07 ` David Daney
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=56CDB912.6000300@arm.com \
--to=marc.zyngier@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).