From: Borislav Petkov <bp@alien8.de>
To: Tyler Baicar <tbaicar@codeaurora.org>
Cc: James Morse <james.morse@arm.com>,
Zhengqiang <zhengqiang10@huawei.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: EDAC, ghes: Make platform-based whitelisting x86-only
Date: Mon, 21 May 2018 19:15:22 +0200 [thread overview]
Message-ID: <20180521171522.GA14289@pd.tnic> (raw)
On Mon, May 21, 2018 at 09:48:23AM -0400, Tyler Baicar wrote:
> I don't see an issue with not printing out the long BIOS statement, but the
> number of DIMM sockets print could still be useful.
Well, if you wanna dump the number of DIMMs - then maybe that line
should issue unconditionally. However, "DIMM sockets" is silly - it
should simply say:
"%d DIMMs detected"
or so.
WARNING: multiple messages have this Message-ID (diff)
From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] EDAC, ghes: Make platform-based whitelisting x86-only
Date: Mon, 21 May 2018 19:15:22 +0200 [thread overview]
Message-ID: <20180521171522.GA14289@pd.tnic> (raw)
In-Reply-To: <b1d606dc-527c-6a7d-ce80-a11ac852a5f9@codeaurora.org>
On Mon, May 21, 2018 at 09:48:23AM -0400, Tyler Baicar wrote:
> I don't see an issue with not printing out the long BIOS statement, but the
> number of DIMM sockets print could still be useful.
Well, if you wanna dump the number of DIMMs - then maybe that line
should issue unconditionally. However, "DIMM sockets" is silly - it
should simply say:
"%d DIMMs detected"
or so.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next reply other threads:[~2018-05-21 17:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 17:15 Borislav Petkov [this message]
2018-05-21 17:15 ` [PATCH] EDAC, ghes: Make platform-based whitelisting x86-only Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2018-05-22 2:10 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 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 11:11 ghes_edac: enable HIP08 platform edac driver Borislav Petkov
2018-05-18 11:11 ` [PATCH] " Borislav Petkov
2018-05-18 7:13 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=20180521171522.GA14289@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@codeaurora.org \
--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.