From: Daniel Ferguson <danielf@os.amperecomputing.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, Shengwei Luo <luoshengwei@huawei.com>,
Jason Tian <jason@os.amperecomputing.com>
Subject: Re: [PATCH v5 0/2] Adds additional information to ARM RAS errors
Date: Thu, 11 Apr 2024 13:43:00 -0700 [thread overview]
Message-ID: <4296a669-ee88-4f6c-aaa2-4416cad5c323@os.amperecomputing.com> (raw)
In-Reply-To: <20240321-b4-arm-ras-error-vendor-info-v5-rc3-v5-0-850f9bfb97a8@os.amperecomputing.com>
On 3/21/2024 3:55 PM, Daniel Ferguson wrote:
> The patch by Shengwei includes most of the justification for this series
> in the commit message. The only thing i've done is add a few conditional compilation
> directives based on feedback from a previous submission attempt. This series adds:
>
> 1) Conditional compilation directives around ARM specific RAS error
> handling routines, so non-ARM platforms are not unnecessarily bloated.
> 2) ARM Processor error section (As defined by UEFI 2.9 N2.4) to tracepoints for userspace
> consumption. This particular patch is a RESEND.
>
> Originally:
> I did a RESEND of Shengwei's V3. I didn't make
> changes, and I didn't rev.
> The original patch: https://lore.kernel.org/lkml/20220214030813.135766-1-lostway@zju.edu.cn/
> Changes since v3:
> Added conditional compilation directives
> previous submission(RESEND): https://lore.kernel.org/lkml/20231214232330.306526-1-danielf@os.amperecomputing.com/
> Changes since v4:
> Rebased on latest linux master.
> No functional changes.
> previous submission: https://lore.kernel.org/linux-kernel/20240226-b4-arm-ras-error-vendor-info-v4-rc3-v4-0-08e0f168fec1@os.amperecomputing.com/
>
Hi Tony,
Thank you for your original comments several months ago for my v3
resend. I'm hoping I can get you to take another peek at this.
Daniel
prev parent reply other threads:[~2024-04-11 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 22:55 Daniel Ferguson
2024-03-21 22:55 ` [PATCH v5 1/2] RAS: ACPI: APEI: add conditional compilation to ARM specific error reporting routines Daniel Ferguson
2024-03-21 22:55 ` [PATCH v5 2/2] RAS: Report ARM processor information to userspace Daniel Ferguson
2024-04-26 11:45 ` Shiju Jose
2024-04-11 20:43 ` Daniel Ferguson [this message]
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=4296a669-ee88-4f6c-aaa2-4416cad5c323@os.amperecomputing.com \
--to=danielf@os.amperecomputing.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=jason@os.amperecomputing.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luoshengwei@huawei.com \
--cc=rafael@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
all inboxes | Powered by JetHome®