From: Talel Shenhar <talel@amazon.com>
To: <robh+dt@kernel.org>, <mark.rutland@arm.com>, <bp@alien8.de>,
<mchehab@kernel.org>, <james.morse@arm.com>, <talel@amazon.com>,
<davem@davemloft.net>, <gregkh@linuxfoundation.org>,
<nicolas.ferre@microchip.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-edac@vger.kernel.org>
Cc: <dwmw@amazon.co.uk>, <benh@kernel.crashing.org>,
<hhhawa@amazon.com>, <ronenk@amazon.com>, <jonnyc@amazon.com>,
<hanochu@amazon.com>, <amirkl@amazon.com>, <barakw@amazon.com>
Subject: [PATCH v2 0/2] Amazon's Annapurna Labs Memory Controller EDAC
Date: Sun, 15 Sep 2019 09:43:53 +0300 [thread overview]
Message-ID: <1568529835-15319-1-git-send-email-talel@amazon.com> (raw)
This series introduces support for Amazon's Annapurna Labs Memory
Controller EDAC driver.
Changes since v1:
=================
- updated dt binding node name and added Rob Reviewed-By
- removed auto selecting of this driver
Talel Shenhar (2):
dt-bindings: edac: al-mc-edac: Amazon's Annapurna Labs Memory
Controller EDAC
EDAC: al-mc-edac: Introduce Amazon's Annapurna Labs Memory Controller
EDAC
.../devicetree/bindings/edac/amazon,al-mc-edac.txt | 24 ++
MAINTAINERS | 7 +
drivers/edac/Kconfig | 7 +
drivers/edac/Makefile | 1 +
drivers/edac/al_mc_edac.c | 382 +++++++++++++++++++++
5 files changed, 421 insertions(+)
create mode 100644 Documentation/devicetree/bindings/edac/amazon,al-mc-edac.txt
create mode 100644 drivers/edac/al_mc_edac.c
--
2.7.4
next reply other threads:[~2019-09-15 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 6:43 Talel Shenhar [this message]
2019-09-15 6:43 ` [PATCH v2 1/2] dt-bindings: edac: al-mc-edac: " Talel Shenhar
2019-09-15 6:43 ` [PATCH v2 2/2] EDAC: al-mc-edac: Introduce " Talel Shenhar
2019-09-18 17:47 ` James Morse
2019-09-19 8:36 ` Shenhar, Talel
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=1568529835-15319-1-git-send-email-talel@amazon.com \
--to=talel@amazon.com \
--cc=amirkl@amazon.com \
--cc=barakw@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=james.morse@arm.com \
--cc=jonnyc@amazon.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
/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
all inboxes | Powered by JetHome®