public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Fan Wu <wufan@codeaurora.org>
Cc: mchehab@kernel.org, james.morse@arm.com, baicar.tyler@gmail.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, john.garry@huawei.com,
	toshi.kani@hpe.com, tanxiaofei@huawei.com,
	wanghuiqiang@huawei.com, shiju.jose@huawei.com
Subject: Re: [PATCH v5] EDAC, ghes: use CPER module handles to locate DIMMs
Date: Sat, 22 Sep 2018 18:37:44 +0200	[thread overview]
Message-ID: <20180922163744.GC26797@zn.tnic> (raw)
In-Reply-To: <1537322340-1860-1-git-send-email-wufan@codeaurora.org>

On Wed, Sep 19, 2018 at 01:59:00AM +0000, Fan Wu wrote:
> For platforms whose firmwares provide valid module handles
> (SMBIOS type 17) in error records, this patch uses the module
> handles to locate corresponding DIMMs and enables per-DIMM
> error counter update.
> 
> Signed-off-by: Fan Wu <wufan@codeaurora.org>
> Reviewed-by: Tyler Baicar <baicar.tyler@gmail.com>
> Reviewed-by: James Morse <james.morse@arm.com>
> Tested-by: Toshi Kani <toshi.kani@hpe.com>
> ---
> 
> Changes from v4:
> Changes from v3:
> * Updated Reviewed-by list
> 
> Changes from v2:
> * Fixed coding style glitch
> * Added Tested-by/Reviewed-by
> 
> Changes from v1:
> *  Changed the new function name to get_dimm_smbios_index
> *  Removed unnecessary checks inside get_dimm_smbios_index
> *  Reverted the change of the DMI handle print
> *  Updated commit message
> 
> ---
>  drivers/edac/ghes_edac.c | 23 +++++++++++++++++++++++
>  include/linux/edac.h     |  2 ++
>  2 files changed, 25 insertions(+)

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

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

      reply	other threads:[~2018-09-22 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  1:59 [PATCH v5] EDAC, ghes: use CPER module handles to locate DIMMs Fan Wu
2018-09-22 16:37 ` 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=20180922163744.GC26797@zn.tnic \
    --to=bp@alien8.de \
    --cc=baicar.tyler@gmail.com \
    --cc=james.morse@arm.com \
    --cc=john.garry@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=shiju.jose@huawei.com \
    --cc=tanxiaofei@huawei.com \
    --cc=toshi.kani@hpe.com \
    --cc=wanghuiqiang@huawei.com \
    --cc=wufan@codeaurora.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