All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: James Morse <james.morse@arm.com>
Cc: Zhengqiang <zhengqiang10@huawei.com>,
	Tyler Baicar <tbaicar@qti.qualcomm.com>,
	mchehab@kernel.org, toshi.kani@hpe.com,
	linux-edac@vger.kernel.org, linuxarm@huawei.com,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: ghes_edac: enable HIP08 platform edac driver
Date: Fri, 18 May 2018 13:11:32 +0200	[thread overview]
Message-ID: <20180518111132.GC17285@pd.tnic> (raw)

On Thu, May 17, 2018 at 07:02:18PM +0100, James Morse wrote:
> v4.17-rc5 has 'return 0' here. Wouldn't this change means no ghes can be
> registered unless ghes_edac is also supported by the platform?
> Shouldn't this be '0' for a silent failure?

https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/commit/?h=for-next&id=cc7f3f132658289b6661ab8294ab08a9d32ea026

> Tested on Seattle and some cranky homebrew-no-DMI firmware:
> Tested-by: James Morse <james.morse@arm.com>
> 
> With the ENODEV/0 thing above:
> Reviewed-by: James Morse <james.morse@arm.com>

Thanks, adding.

WARNING: multiple messages have this Message-ID (diff)
From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ghes_edac: enable HIP08 platform edac driver
Date: Fri, 18 May 2018 13:11:32 +0200	[thread overview]
Message-ID: <20180518111132.GC17285@pd.tnic> (raw)
In-Reply-To: <8602b133-e0fa-57e2-5159-9d34a1ded85f@arm.com>

On Thu, May 17, 2018 at 07:02:18PM +0100, James Morse wrote:
> v4.17-rc5 has 'return 0' here. Wouldn't this change means no ghes can be
> registered unless ghes_edac is also supported by the platform?
> Shouldn't this be '0' for a silent failure?

https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/commit/?h=for-next&id=cc7f3f132658289b6661ab8294ab08a9d32ea026

> Tested on Seattle and some cranky homebrew-no-DMI firmware:
> Tested-by: James Morse <james.morse@arm.com>
> 
> With the ENODEV/0 thing above:
> Reviewed-by: James Morse <james.morse@arm.com>

Thanks, adding.

-- 
Regards/Gruss,
    Boris.

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

             reply	other threads:[~2018-05-18 11:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 11:11 Borislav Petkov [this message]
2018-05-18 11:11 ` [PATCH] ghes_edac: enable HIP08 platform edac driver Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2018-05-22  2:10 EDAC, ghes: Make platform-based whitelisting x86-only Tyler Baicar
2018-05-22  2:10 ` [PATCH] " Tyler Baicar
2018-05-21 20:44 Borislav Petkov
2018-05-21 20:44 ` [PATCH] " Borislav Petkov
2018-05-21 20:34 Tyler Baicar
2018-05-21 20:34 ` [PATCH] " Tyler Baicar
2018-05-21 17:15 Borislav Petkov
2018-05-21 17:15 ` [PATCH] " Borislav Petkov
2018-05-21 13:48 Tyler Baicar
2018-05-21 13:48 ` [PATCH] " Tyler Baicar
2018-05-21  9:39 Zhengqiang
2018-05-21  9:39 ` [PATCH] " Zhengqiang
2018-05-18 11:20 Borislav Petkov
2018-05-18 11:20 ` [PATCH] " Borislav Petkov
2018-05-18  7:13 ghes_edac: enable HIP08 platform edac driver Zhengqiang
2018-05-18  7:13 ` [PATCH] " Zhengqiang
2018-05-17 18:02 James Morse
2018-05-17 18:02 ` [PATCH] " James Morse
2018-05-16 18:29 Borislav Petkov
2018-05-16 18:29 ` [PATCH] " Borislav Petkov
2018-05-16 13:38 James Morse
2018-05-16 13:38 ` [PATCH] " James Morse
2018-05-14 16:47 Borislav Petkov
2018-05-14 16:47 ` [PATCH] " Borislav Petkov
2018-05-14 15:12 James Morse
2018-05-14 15:12 ` [PATCH] " James Morse
2018-05-14  9:47 Borislav Petkov
2018-05-14  4:11 Zhengqiang
2018-05-11 12:19 Borislav Petkov
2018-05-11 11:52 Zhengqiang

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=20180518111132.GC17285@pd.tnic \
    --to=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mchehab@kernel.org \
    --cc=tbaicar@qti.qualcomm.com \
    --cc=toshi.kani@hpe.com \
    --cc=zhengqiang10@huawei.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.