From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Mario Limonciello <mario.limonciello@amd.com>
Cc: "open list:X86 PLATFORM DRIVERS"
<platform-driver-x86@vger.kernel.org>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
al0uette@outlook.com
Subject: Re: [PATCH 1/3] platform/x86/amd: pmf: Decrease error message to debug
Date: Tue, 16 Apr 2024 15:31:55 +0300 [thread overview]
Message-ID: <171327071596.3662.6978319849013106734.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20240410140956.385-1-mario.limonciello@amd.com>
On Wed, 10 Apr 2024 09:09:54 -0500, Mario Limonciello wrote:
> ASUS ROG Zephyrus G14 doesn't have _CRS in AMDI0102 device and so
> there are no resources to walk. This is expected behavior because
> it doesn't support Smart PC. Decrease error message to debug.
>
>
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/3] platform/x86/amd: pmf: Decrease error message to debug
commit: 03cea821b82cbf0ee4a285f9dca6cc1d660dbef3
[2/3] platform/x86/amd: pmf: Add infrastructure for quirking supported funcs
commit: ed13f622bcd594d6cefd6239b1722ed8b84ba98f
[3/3] platform/x86/amd: pmf: Add quirk for ROG Zephyrus G14
commit: 9d893061ed68820de24b572d1e193b5e4737f2e0
--
i.
prev parent reply other threads:[~2024-04-16 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 14:09 [PATCH 1/3] platform/x86/amd: pmf: Decrease error message to debug Mario Limonciello
2024-04-10 14:09 ` [PATCH 2/3] platform/x86/amd: pmf: Add infrastructure for quirking supported funcs Mario Limonciello
2024-04-10 14:09 ` [PATCH 3/3] platform/x86/amd: pmf: Add quirk for ROG Zephyrus G14 Mario Limonciello
2024-04-15 13:53 ` [PATCH 1/3] platform/x86/amd: pmf: Decrease error message to debug Hans de Goede
2024-04-16 12:31 ` Ilpo Järvinen [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=171327071596.3662.6978319849013106734.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=al0uette@outlook.com \
--cc=hdegoede@redhat.com \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).