From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: EDAC on arm64
Date: Mon, 2 Mar 2015 10:59:32 +0000 [thread overview]
Message-ID: <20150302105919.GA4434@arm.com> (raw)
In-Reply-To: <54F11133.70909@redhat.com>
On Sat, Feb 28, 2015 at 12:52:03AM +0000, Jon Masters wrote:
> Have you considered reviving the patch you posted previously for EDAC
> support (the atomic_scrub read/write test piece dependency)?
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/249039.html
Well, we'd need a way to handle the non-coherent DMA case and it's really
not clear how to fix that.
Will
next prev parent reply other threads:[~2015-03-02 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 0:52 EDAC on arm64 Jon Masters
2015-03-02 10:59 ` Will Deacon [this message]
2015-03-02 14:58 ` Catalin Marinas
2015-03-02 16:34 ` Rob Herring
2015-03-02 18:03 ` Catalin Marinas
2015-03-02 22:27 ` Catalin Marinas
2015-03-02 22:57 ` Rob Herring
2015-03-03 11:01 ` Catalin Marinas
2015-03-03 15:56 ` Rob Herring
2015-03-02 19:40 ` Arnd Bergmann
2015-03-02 22:25 ` Catalin Marinas
2015-03-03 9:23 ` Arnd Bergmann
2015-03-03 10:57 ` Catalin Marinas
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=20150302105919.GA4434@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).