public inbox for linux-kernel@vger.kernel.org
 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,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC, altera: Fix S10 Double Bit Error Notification
Date: Sat, 23 Mar 2019 10:15:05 +0100	[thread overview]
Message-ID: <20190323091505.GC23698@zn.tnic> (raw)
In-Reply-To: <1552490842-25440-1-git-send-email-thor.thayer@linux.intel.com>

On Wed, Mar 13, 2019 at 10:27:22AM -0500, thor.thayer@linux.intel.com wrote:
> From: Thor Thayer <thor.thayer@linux.intel.com>
> 
> Stratix10 Double Bit Error Address was always read from
> SDRAM Address register instead of each device's Address
> register.
> To determine which device had the DBE, cycle through
> the EDAC devices comparing the DBE value to the db_irq
> value. Once found, report the DBE Address from the device
> registers as well as the device name.
> Finally, notify the system via an SMC call and indicate
> the panic should result in a system reboot.
> Change a run-time check to a Stratix10 compile-time check
> for a clean SMC notification.
> 
> Fixes: d5fc9125566c ("EDAC, altera: Combine Stratix10 and Arria10 probe functions")
> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
> ---
>  drivers/edac/altera_edac.c | 69 ++++++++++++++++++++++++++++++++++------------
>  drivers/edac/altera_edac.h | 20 ++++++++++++++
>  2 files changed, 72 insertions(+), 17 deletions(-)

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

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

      reply	other threads:[~2019-03-23  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 15:27 [PATCH] EDAC, altera: Fix S10 Double Bit Error Notification thor.thayer
2019-03-23  9:15 ` 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=20190323091505.GC23698@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox