From: Borislav Petkov <bp@alien8.de>
To: Aili Yao <yaoaili@kingsoft.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, tony.luck@intel.com,
james.morse@arm.com, linux-acpi@vger.kernel.org,
linux-edac@vger.kernel.org, yangfeng1@kingsoft.com,
CHENGUOMIN@kingsoft.com
Subject: Re: [PATCH v2] Dump cper error table in mce_panic
Date: Wed, 18 Nov 2020 13:45:38 +0100 [thread overview]
Message-ID: <20201118124538.GI7472@zn.tnic> (raw)
In-Reply-To: <20201117175804.39bbbdc3.yaoaili@kingsoft.com>
On Tue, Nov 17, 2020 at 05:58:04PM +0800, Aili Yao wrote:
> Subject: [PATCH v2] Dump cper error table in mce_panic
>
> For X86_MCE, When BIOS option WHEA memory log is enabled,if there is a
> ...
This commit message makes no sense to me and I have no clue what you're
trying to "fix". So before you do anything, please describe the problem
you're seeing first using this structure:
Problem is A.
It happens because of B.
Fix it by doing C.
(Potentially do D).
When you do that, use simple english sentences and not complex ones.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-11-18 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:50 [PATCH] Dump cper error table in mce_panic yaoaili126
2020-11-04 10:16 ` kernel test robot
2020-11-06 19:35 ` James Morse
2020-11-18 3:12 ` Aili Yao
2020-11-17 9:58 ` [PATCH v2] " Aili Yao
2020-11-18 12:45 ` Borislav Petkov [this message]
2020-11-19 5:40 ` Aili Yao
2020-11-19 17:45 ` Borislav Petkov
2020-11-20 3:40 ` Aili Yao
2020-11-20 9:22 ` Aili Yao
2020-11-20 10:24 ` Borislav Petkov
2021-01-28 12:01 ` Aili Yao
2021-01-28 17:22 ` Luck, Tony
2021-02-23 9:18 ` Aili Yao
2021-02-23 19:32 ` Luck, Tony
2021-02-24 9:56 ` Aili Yao
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=20201118124538.GI7472@zn.tnic \
--to=bp@alien8.de \
--cc=CHENGUOMIN@kingsoft.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=yangfeng1@kingsoft.com \
--cc=yaoaili@kingsoft.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