From: Dinh Nguyen <dinguyen@kernel.org>
To: Borislav Petkov <bp@alien8.de>, thor.thayer@linux.intel.com
Cc: linux@armlinux.org.uk, mchehab@kernel.org, james.morse@arm.com,
linux-edac@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/2] Independent SOCFPGA SDRAM EDAC config
Date: Tue, 26 Feb 2019 08:59:43 -0600 [thread overview]
Message-ID: <17733148-82fd-e119-3525-c2d580fabc99@kernel.org> (raw)
In-Reply-To: <20190225204244.GJ26145@zn.tnic>
Hi Boris,
On 2/25/19 2:42 PM, Borislav Petkov wrote:
> On Mon, Feb 25, 2019 at 12:56:44PM -0600, thor.thayer@linux.intel.com wrote:
>> From: Thor Thayer <thor.thayer@linux.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?
>
If you don't mind, I'll take the defconfig patch to avoid any conflicts.
Thanks,
Dinh
next prev parent reply other threads:[~2019-02-26 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 18:56 [PATCHv2 0/2] Independent SOCFPGA SDRAM EDAC config thor.thayer
2019-02-25 18:56 ` [PATCHv2 1/2] EDAC, altera: Add separate " thor.thayer
2019-02-25 18:56 ` [PATCHv2 2/2] ARM: socfpga_defconfig: enable EDAC by default thor.thayer
2019-02-25 20:42 ` [PATCHv2 0/2] Independent SOCFPGA SDRAM EDAC config Borislav Petkov
2019-02-26 14:59 ` Dinh Nguyen [this message]
2019-02-26 17:47 ` 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=17733148-82fd-e119-3525-c2d580fabc99@kernel.org \
--to=dinguyen@kernel.org \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mchehab@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