From: Borislav Petkov <bp@alien8.de>
To: Talel Shenhar <talel@amazon.com>
Cc: mchehab@kernel.org, james.morse@arm.com, davem@davemloft.net,
gregkh@linuxfoundation.org, nicolas.ferre@microchip.com,
robh+dt@kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, will@kernel.org,
linux-edac@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, hhhawa@amazon.com,
ronenk@amazon.com, jonnyc@amazon.com, hanochu@amazon.com,
eitan@amazon.com
Subject: Re: [PATCH v10 0/2] Amazon's Annapurna Labs Memory Controller EDAC
Date: Mon, 17 Aug 2020 10:31:13 +0200 [thread overview]
Message-ID: <20200817083113.GA549@zn.tnic> (raw)
In-Reply-To: <20200816185551.19108-1-talel@amazon.com>
On Sun, Aug 16, 2020 at 09:55:49PM +0300, Talel Shenhar wrote:
> 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
>
> .../bindings/edac/amazon,al-mc-edac.yaml | 67 ++++
> MAINTAINERS | 7 +
> drivers/edac/Kconfig | 7 +
> drivers/edac/Makefile | 1 +
> drivers/edac/al_mc_edac.c | 354 ++++++++++++++++++
> 5 files changed, 436 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/edac/amazon,al-mc-edac.yaml
> create mode 100644 drivers/edac/al_mc_edac.c
Applied, thanks.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2020-08-17 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 18:55 [PATCH v10 0/2] Amazon's Annapurna Labs Memory Controller EDAC Talel Shenhar
2020-08-16 18:55 ` [PATCH v10 1/2] dt-bindings: edac: al-mc-edac: " Talel Shenhar
2020-08-16 18:55 ` [PATCH v10 2/2] EDAC: al-mc-edac: Introduce " Talel Shenhar
2020-08-17 8:31 ` Borislav Petkov [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=20200817083113.GA549@zn.tnic \
--to=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eitan@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=james.morse@arm.com \
--cc=jonnyc@amazon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 \
--cc=talel@amazon.com \
--cc=will@kernel.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