From: Xie XiuQi <xiexiuqi@huawei.com>
To: Borislav Petkov <bp@alien8.de>, James Morse <james.morse@arm.com>
Cc: <tony.luck@intel.com>, <linux-edac@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] trace: ras: print the raw data of arm processor error info
Date: Mon, 13 Jan 2020 22:10:11 +0800 [thread overview]
Message-ID: <3086a22d-6d66-df74-5878-60a8fc0f1499@huawei.com> (raw)
In-Reply-To: <20200109114603.GC5603@zn.tnic>
Hi James,
What do you think of this patch?
On 2020/1/9 19:46, Borislav Petkov wrote:
>> );
>>
>> /*
>> --
> That's for ARM folks to decide whether they wanna shuffle raw error
> records into userspace like that. CCed.
next prev parent reply other threads:[~2020-01-13 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 12:11 [PATCH] trace: ras: print the raw data of arm processor error info Xie XiuQi
2019-12-16 10:17 ` Denverton decoding: BIOS performance setting Hermann Ruckerbauer
2020-01-09 11:46 ` [PATCH] trace: ras: print the raw data of arm processor error info Borislav Petkov
2020-01-13 14:10 ` Xie XiuQi [this message]
2020-02-26 15:14 ` James Morse
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=3086a22d-6d66-df74-5878-60a8fc0f1499@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).