From: Sven van Ashbrook <svenva@chromium.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
Rajneesh Bhardwaj <irenic.rajneesh@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
"rrangel@chromium.org" <rrangel@chromium.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>,
Rafael J Wysocki <rjw@rjwysocki.net>,
Rajat Jain <rajatja@google.com>,
David E Box <david.e.box@intel.com>,
Mark Gross <markgross@kernel.org>
Subject: Re: [PATCH v1] platform/x86: intel_pmc_core: promote S0ix failure warn() to WARN()
Date: Mon, 31 Oct 2022 16:20:35 -0400 [thread overview]
Message-ID: <CAM7w-FVC3pcjROQA1ra5Py9A9BrQotrwJNiykNSFkUN-p8_DGw@mail.gmail.com> (raw)
In-Reply-To: <2124934d-a8f1-59fa-1958-28472d06d2d6@redhat.com>
On Mon, Oct 31, 2022 at 4:15 PM Hans de Goede <hdegoede@redhat.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.
next prev parent reply other threads:[~2022-10-31 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 15:19 [PATCH v1] platform/x86: intel_pmc_core: promote S0ix failure warn() to WARN() Sven van Ashbrook
2022-10-27 15:40 ` Hans de Goede
2022-10-27 15:47 ` Limonciello, Mario
2022-10-27 15:51 ` Sven van Ashbrook
[not found] ` <CAE2upjS6qRGRcuVYuAB5DMf66A7VcfCKKYEkpsr1My7RnKDFtQ@mail.gmail.com>
2022-10-29 4:11 ` Sven van Ashbrook
2022-10-31 19:39 ` Limonciello, Mario
2022-10-31 20:15 ` Hans de Goede
2022-10-31 20:20 ` Sven van Ashbrook [this message]
[not found] ` <CACK8Z6E7=xt118d47FTpmgKHgUBgH48FQzTi5iL90C3MjHb-3Q@mail.gmail.com>
2022-10-31 20:55 ` Limonciello, Mario
2022-11-01 17:24 ` Sven van Ashbrook
2022-11-01 20:30 ` David E. Box
2022-11-01 1:38 ` Sven van Ashbrook
2022-11-01 1:58 ` Mario Limonciello
2022-11-01 13:50 ` Sven van Ashbrook
2022-10-27 16:37 ` David E. Box
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=CAM7w-FVC3pcjROQA1ra5Py9A9BrQotrwJNiykNSFkUN-p8_DGw@mail.gmail.com \
--to=svenva@chromium.org \
--cc=Mario.Limonciello@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=david.e.box@intel.com \
--cc=hdegoede@redhat.com \
--cc=irenic.rajneesh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajatja@google.com \
--cc=rajneesh.bhardwaj@intel.com \
--cc=rjw@rjwysocki.net \
--cc=rrangel@chromium.org \
/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).