[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190225204244.GJ26145@zn.tnic>
Date: Mon, 25 Feb 2019 21:42:44 +0100
From: Borislav Petkov <bp@...en8.de>
To: thor.thayer@...ux.intel.com
Cc: dinguyen@...nel.org, linux@...linux.org.uk, mchehab@...nel.org,
james.morse@....com, linux-edac@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 0/2] Independent SOCFPGA SDRAM EDAC config
On Mon, Feb 25, 2019 at 12:56:44PM -0600, thor.thayer@...ux.intel.com wrote:
> From: Thor Thayer <thor.thayer@...ux.intel.com>
>
> Most users want EDAC support so make it the default.
>
> SOCFPGA SDRAM EDAC reporting was enabled by the parent EDAC
> config (CONFIG_ALTERA_EDAC) since initial customers always
> wanted SDRAM EDAC enabled.
> There are cases where the SDRAM needs to be disabled while
> the other block EDACs remain enabled.
> This patch set 1) splits out the SDRAM EDAC into a separate
> config and 2) enables all the EDAC blocks by default for
> 32 bit SOCFPGA.
>
> V2 Changes
> Rebase socfpga_defconfig against arm-soc/arm/defconfig
>
> Thor Thayer (2):
> EDAC, altera: Add separate SDRAM EDAC config
> ARM: socfpga_defconfig: enable EDAC by default
Am I supposed to take the second patch too or is it going through Dinh's
tree?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists