From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: bp@alien8.de, mchehab@kernel.org, linux-edac@vger.kernel.org,
mpe@ellerman.id.au
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v3 0/3] EDAC: mv64x60: updates
Date: Tue, 30 May 2017 09:21:39 +1200 [thread overview]
Message-ID: <20170529212142.25572-1-chris.packham@alliedtelesis.co.nz> (raw)
I'm looking at making use of the mv64x60_edac driver for the armada processors.
It appears that at least the DRAM ECC error reporting is the same block from
the old Marvell Discovery class of processors. On the ARM side I need to get
the error interrupts exposed first before I can send my second set of changes
for this driver but this first set is just a series of cleanups.
Chris Packham (3):
EDAC: mv64x60: check driver registration success
EDAC: mv64x60: Fix pdata->name
EDAC: mv64x60: replace in_le32/out_le32 with readl/writel
drivers/edac/mv64x60_edac.c | 94 +++++++++++++++++++++++----------------------
1 file changed, 49 insertions(+), 45 deletions(-)
--
2.13.0
next reply other threads:[~2017-05-29 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 21:21 Chris Packham [this message]
2017-05-29 21:21 ` [PATCH v3 1/3] EDAC: mv64x60: check driver registration success Chris Packham
2017-06-07 5:29 ` Chris Packham
2017-06-07 9:54 ` Borislav Petkov
2017-05-29 21:21 ` [PATCH v3 2/3] EDAC: mv64x60: Fix pdata->name Chris Packham
2017-05-29 21:21 ` [PATCH v3 3/3] EDAC: mv64x60: replace in_le32/out_le32 with readl/writel Chris Packham
2017-05-30 7:57 ` [PATCH v3 0/3] EDAC: mv64x60: updates Borislav Petkov
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=20170529212142.25572-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchehab@kernel.org \
--cc=mpe@ellerman.id.au \
/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).