From: Huang Rui <ray.huang@amd.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v1 0/2] ACPI: bus: Fix platform-level _OSC handling and avoid CPPC is not supportedg
Date: Thu, 17 Mar 2022 16:08:24 +0800 [thread overview]
Message-ID: <YjLseFErjHeKkluI@amd.com> (raw)
In-Reply-To: <4734682.31r3eYUQgx@kreacher>
On Wed, Mar 16, 2022 at 01:35:23PM +0100, Rafael J. Wysocki wrote:
> Hi All,
>
> The following two patches revert a commit that caused the handling of
> platform-level _OSC to fail in some legitimate cases and address the
> CPPC handling breakage that was the motivation for the reverted commit.
>
> Please refer to the patch changelogs for details.
>
Series are Acked-by: Huang Rui <ray.huang@amd.com>
next prev parent reply other threads:[~2022-03-17 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 12:35 [PATCH v1 0/2] ACPI: bus: Fix platform-level _OSC handling and avoid CPPC is not supported Rafael J. Wysocki
2022-03-16 12:37 ` [PATCH v1 1/2] Revert "ACPI: Pass the same capabilities to the _OSC regardless of the query flag" Rafael J. Wysocki
2022-03-16 12:39 ` [PATCH v1 2/2] ACPI: bus: Avoid using CPPC if not supported by firmware Rafael J. Wysocki
2022-03-16 15:44 ` [PATCH v1 0/2] ACPI: bus: Fix platform-level _OSC handling and avoid CPPC is not supported Limonciello, Mario
2022-03-17 8:08 ` Huang Rui [this message]
2022-03-17 11:43 ` Mika Westerberg
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=YjLseFErjHeKkluI@amd.com \
--to=ray.huang@amd.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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).