From: David Lazar <dlazar@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: stable@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
Greg KH <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.5.y] platform/x86: Add s2idle quirk for more Lenovo laptops
Date: Tue, 31 Oct 2023 12:10:55 +0100 [thread overview]
Message-ID: <ZUDgv5ZyhvyLh5JD@localhost> (raw)
In-Reply-To: <f10297db-3a65-4e61-8f59-3f029e69dbb0@amd.com>
On Mon, 30 Oct 2023 16:30, Mario Limonciello wrote:
> In this case are there modifications or is a clean cherry-pick? If it's not
> a clean cherry pick, why?
This wasn't a clean cherry pick because the code has been moved
from drivers/platform/x86/amd/pmc-quirks.c in 6.5.y
to drivers/platform/x86/amd/pmc/pmc-quirks.c in 6.6.y.
> If it's just missing another system in the quirk list it's cleaner to
> backport that missing system and then have a clean pick.
In this case (the 6.5 patch) there was no missing system in the quirks
list. However, in the 6.1 version, the HP system *is* missing from
the list (it looks like the patch that added that system wasn't
backported to 6.1). But even adding that system wouldn't result in a
clean cherry pick, given that the code had been moved once before
from drivers/platform/x86/thinkpad_acpi.c in 6.1.y
to drivers/platform/x86/amd/pmc-quirks.c in 6.5.y.
I had refrained from adding the missing system also in order to stay
close to the upstream patch.
In any case, I see Sasha and Greg are already working on these patches,
so I'll leave them alone for now, to not generate more work for them.
Thanks for your help, everyone, and please let me know if there's
anything else I should do.
-=[david]=-
next prev parent reply other threads:[~2023-10-31 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 21:12 [PATCH 6.5.y] platform/x86: Add s2idle quirk for more Lenovo laptops David Lazar
2023-10-30 21:30 ` Mario Limonciello
2023-10-31 11:10 ` David Lazar [this message]
2023-10-31 12:59 ` Mario Limonciello
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=ZUDgv5ZyhvyLh5JD@localhost \
--to=dlazar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=sashal@kernel.org \
--cc=stable@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