From: Thor Thayer <thor.thayer@linux.intel.com>
To: Dinh Nguyen <dinguyen@kernel.org>,
bp@alien8.de, linux@armlinux.org.uk, mchehab@kernel.org,
james.morse@arm.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: socfpga_defconfig: enable EDAC by default
Date: Mon, 25 Feb 2019 12:57:37 -0600 [thread overview]
Message-ID: <78bd26f7-861b-0493-c8ed-ccb7a6673825@linux.intel.com> (raw)
In-Reply-To: <ed55288c-458a-b770-423e-3691c020f840@kernel.org>
On 2/25/19 11:36 AM, Dinh Nguyen wrote:
> Hi Thor,
>
> On 2/19/19 12:59 PM, thor.thayer@linux.intel.com wrote:
>> From: Thor Thayer <thor.thayer@linux.intel.com>
>>
>> Enable the different ECC blocks by default on Cyclone5
>> and Arria10.
>>
>> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
>> ---
>> arch/arm/configs/socfpga_defconfig | 36 ++++++++++++++++++++++--------------
>> 1 file changed, 22 insertions(+), 14 deletions(-)
>>
>
> Looks like you did a 'make savedefconfig' on this as well? can you
> please rebase your patch to the arm/defconfig on the arm-soc tree?
>
> Thanks,
> Dinh
>
Yes. I'll send a V2 shortly. Thanks for reviewing.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-25 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 18:59 [PATCH 0/2] Distinct SOCFPGA SDRAM EDAC config thor.thayer
2019-02-19 18:59 ` [PATCH 1/2] EDAC, altera: Add separate " thor.thayer
2019-02-19 18:59 ` [PATCH 2/2] ARM: socfpga_defconfig: enable EDAC by default thor.thayer
2019-02-25 17:36 ` Dinh Nguyen
2019-02-25 18:57 ` Thor Thayer [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=78bd26f7-861b-0493-c8ed-ccb7a6673825@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=bp@alien8.de \
--cc=dinguyen@kernel.org \
--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 \
/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).