From: Borislav Petkov <bp@alien8.de>
To: thor.thayer@linux.intel.com
Cc: mchehab@kernel.org, james.morse@arm.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [2/2] EDAC, altera: Initialize peripheral FIFOs in probe()
Date: Fri, 29 Mar 2019 11:51:12 +0100 [thread overview]
Message-ID: <20190329105112.GD21152@zn.tnic> (raw)
On Tue, Mar 26, 2019 at 04:29:31PM -0500, thor.thayer@linux.intel.com wrote:
> From: Thor Thayer <thor.thayer@linux.intel.com>
>
> The FIFO memory and ECC initialization doesn't need to be
> done as a separate operation early in the startup.
>
> Improve the Arria10 and Stratix10 peripheral FIFO init
> by initializing memory and enabling ECC as part of the
> device driver initialization.
>
> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
> ---
> drivers/edac/altera_edac.c | 162 +++++++++++++++++++++++++--------------------
> 1 file changed, 91 insertions(+), 71 deletions(-)
Both applied,
thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: thor.thayer@linux.intel.com
Cc: mchehab@kernel.org, james.morse@arm.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] EDAC, altera: Initialize peripheral FIFOs in probe()
Date: Fri, 29 Mar 2019 11:51:12 +0100 [thread overview]
Message-ID: <20190329105112.GD21152@zn.tnic> (raw)
In-Reply-To: <1553635771-32693-2-git-send-email-thor.thayer@linux.intel.com>
On Tue, Mar 26, 2019 at 04:29:31PM -0500, thor.thayer@linux.intel.com wrote:
> From: Thor Thayer <thor.thayer@linux.intel.com>
>
> The FIFO memory and ECC initialization doesn't need to be
> done as a separate operation early in the startup.
>
> Improve the Arria10 and Stratix10 peripheral FIFO init
> by initializing memory and enabling ECC as part of the
> device driver initialization.
>
> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
> ---
> drivers/edac/altera_edac.c | 162 +++++++++++++++++++++++++--------------------
> 1 file changed, 91 insertions(+), 71 deletions(-)
Both applied,
thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next reply other threads:[~2019-03-29 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 10:51 Borislav Petkov [this message]
2019-03-29 10:51 ` [PATCH 2/2] EDAC, altera: Initialize peripheral FIFOs in probe() Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2019-03-26 21:29 [2/2] " thor.thayer
2019-03-26 21:29 ` [PATCH 2/2] " thor.thayer
2019-03-26 21:29 [1/2] EDAC, altera: Less Intrusive Error Injection thor.thayer
2019-03-26 21:29 ` [PATCH 1/2] " thor.thayer
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=20190329105112.GD21152@zn.tnic \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.