[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM7w-FVC3pcjROQA1ra5Py9A9BrQotrwJNiykNSFkUN-p8_DGw@mail.gmail.com>
Date: Mon, 31 Oct 2022 16:20:35 -0400
From: Sven van Ashbrook <svenva@...omium.org>
To: Hans de Goede <hdegoede@...hat.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@....com>,
Rajneesh Bhardwaj <irenic.rajneesh@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@....com>,
"rrangel@...omium.org" <rrangel@...omium.org>,
"platform-driver-x86@...r.kernel.org"
<platform-driver-x86@...r.kernel.org>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@...el.com>,
Rafael J Wysocki <rjw@...ysocki.net>,
Rajat Jain <rajatja@...gle.com>,
David E Box <david.e.box@...el.com>,
Mark Gross <markgross@...nel.org>
Subject: Re: [PATCH v1] platform/x86: intel_pmc_core: promote S0ix failure
warn() to WARN()
On Mon, Oct 31, 2022 at 4:15 PM Hans de Goede <hdegoede@...hat.com> wrote:
>
> Something like this does indeed sound like a nice solution for this.
Agreed, much nicer than letting the monitoring infrastructure hunt for
certain dmesg strings, for sure. Thank you David for the suggestion,
and Mario for the opening ideas.
Powered by blists - more mailing lists