From: Boris Petkov <bp@alien8.de>
To: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
tony.luck@intel.com
Subject: Re: [PATCH v2] RAS: Report ARM processor information to userspace
Date: Wed, 26 Jan 2022 10:54:11 +0000 [thread overview]
Message-ID: <BB2F2992-E9FB-435D-B33C-2334E3D9F3D3@alien8.de> (raw)
In-Reply-To: <20220126030906.56765-1-lostway@zju.edu.cn>
On January 26, 2022 3:09:06 AM UTC, lostway@zju.edu.cn wrote:
>From: Shengwei Luo <luoshengwei@huawei.com>
>
>The ARM processor error section includes several ARM processor error
>information, several ARM processor context information and several
>vendor specific error information structures. In addition to these
>info, there are error severity and cpu logical index about the event.
>Report all of these information to userspace via perf i/f.
A patch commit message needs to explain why a change is being done, not what is being done. The "what" I can see most of the time.
--
Sent from a small device: formatting sux and brevity is inevitable.
next prev parent reply other threads:[~2022-01-26 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 3:09 [PATCH v2] RAS: Report ARM processor information to userspace lostway
2022-01-26 10:54 ` Boris Petkov [this message]
2022-02-01 18:33 ` Mark Rutland
[not found] ` <185FED5B-4C49-4DE1-95D8-594E81B57E31@zju.edu.cn>
2022-02-09 12:01 ` Borislav Petkov
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=BB2F2992-E9FB-435D-B33C-2334E3D9F3D3@alien8.de \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).