[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6889074f38d5e_48e510076@dwillia2-xfh.jf.intel.com.notmuch>
Date: Tue, 29 Jul 2025 10:39:27 -0700
From: <dan.j.williams@...el.com>
To: "Koralahalli Channabasappa, Smita"
<Smita.KoralahalliChannabasappa@....com>, Marc Herbert
<marc.herbert@...ux.intel.com>, <linux-efi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>
CC: Ard Biesheuvel <ardb@...nel.org>, Alison Schofield
<alison.schofield@...el.com>, Vishal Verma <vishal.l.verma@...el.com>, "Ira
Weiny" <ira.weiny@...el.com>, Dan Williams <dan.j.williams@...el.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>, Yazen Ghannam
<yazen.ghannam@....com>, Terry Bowman <terry.bowman@....com>, Dave Jiang
<dave.jiang@...el.com>, <tony.luck@...el.com>, Gregory Price
<gourry@...rry.net>
Subject: Re: "invalid agent type: 1" in acpi/ghes, cper: Recognize and cache
CXL Protocol errors
Koralahalli Channabasappa, Smita wrote:
[..]
> >> I agree that a brief comment explaining this rationale would help. I'm
> >> okay if you plan to include a fixup for this along with the one for
> >> the device serial number.
> >
> > If I understood you correctly, I think a different error message
> > would be much better than a comment. Like this?
>
> Yeah looks good to me. Thanks for fixing this!
Wait, I was thinking to delete these messages. The rationale being, why
continue to harass the system owner indefinetly with the fact that their
BIOS is emitting kernel unsupported CPER records? The value of that
unactionable report is look. This feels like dev_dbg_ratelimited(), or
dev_warn_once() at most.
Powered by blists - more mailing lists