devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: thor.thayer@linux.intel.com
Cc: mchehab@kernel.org, james.morse@arm.com, dinguyen@kernel.org,
	robh+dt@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Add Stratix10 OCRAM & SDMMC EDAC Support
Date: Fri, 10 May 2019 16:34:13 +0200	[thread overview]
Message-ID: <20190510143413.GC29927@zn.tnic> (raw)
In-Reply-To: <1556030197-24534-1-git-send-email-thor.thayer@linux.intel.com>

On Tue, Apr 23, 2019 at 09:36:33AM -0500, thor.thayer@linux.intel.com wrote:
> From: Thor Thayer <thor.thayer@linux.intel.com>
> 
> This patch series adds EDAC support for the Stratix10 OCRAM
> and SDMMC peripherals.
> 
> Thor Thayer (4):
>   EDAC, altera: Add Stratix10 OCRAM ECC support
>   arm64: dts: stratix10: Add OCRAM EDAC node
>   EDAC, altera: Add Stratix10 SDMMC support
>   arm64: dts: stratix10: Add SDMMC EDAC node
> 
>  arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi  |  8 ++++
>  .../boot/dts/altera/socfpga_stratix10_socdk.dts    | 11 ++++++
>  drivers/edac/altera_edac.c                         | 43 ++++++++++++++++++++--
>  3 files changed, 59 insertions(+), 3 deletions(-)
> 
> -- 

All 4 queued locally, will appear after -rc1 releases.

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

      parent reply	other threads:[~2019-05-10 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 14:36 [PATCH 0/4] Add Stratix10 OCRAM & SDMMC EDAC Support thor.thayer
2019-04-23 14:36 ` [PATCH 1/4] EDAC, altera: Add Stratix10 OCRAM ECC support thor.thayer
2019-04-23 14:36 ` [PATCH 2/4] arm64: dts: stratix10: Add OCRAM EDAC node thor.thayer
2019-05-06 15:17   ` Dinh Nguyen
2019-04-23 14:36 ` [PATCH 3/4] EDAC, altera: Add Stratix10 SDMMC support thor.thayer
2019-04-23 14:36 ` [PATCH 4/4] arm64: dts: stratix10: Add SDMMC EDAC node thor.thayer
2019-05-06 15:17   ` Dinh Nguyen
2019-05-10 14:34 ` 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=20190510143413.GC29927@zn.tnic \
    --to=bp@alien8.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thor.thayer@linux.intel.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;
as well as URLs for NNTP newsgroup(s).