All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Lazar <dlazar@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	Mark Gross <markgross@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	Mark Pearson <mpearson-lenovo@squebb.ca>
Subject: Re: [PATCH] platform/x86: Add s2idle quirk for more Lenovo laptops
Date: Sun, 29 Oct 2023 14:30:57 +0100	[thread overview]
Message-ID: <ZT5ekV2JaWhf5bWF@localhost> (raw)
In-Reply-To: <e2370602-256a-4c30-b73f-1552d7d8bf22@redhat.com>

On Thu, 26 Oct 2023, Hans de Goede wrote:
> I'll prep + send a fixes pull-req to Linus
> with just this single patch tomorrow.

The patch recently landed in Linus' tree, so thanks for that.

I didn't realize that the fixes for this laptop family would be also
considered for the stable trees, so I hadn't Cc-ed
stable@vger.kernel.org in my original patch.  But I now see that gregkh
picked up Thomas' fix for stable-6.1 and stable-6.5:

https://www.spinics.net/lists/stable-commits/msg321665.html

So, should we also forward this patch to gregkh, to make these laptops
work with the stable trees?  What's the process for that?

Thanks,
-=[david]=-

  parent reply	other threads:[~2023-10-29 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 19:30 [PATCH] platform/x86: Add s2idle quirk for more Lenovo laptops David Lazar
2023-10-25 22:06 ` Mario Limonciello
2023-10-25 22:38   ` Mark Pearson
2023-10-26  8:10 ` Hans de Goede
2023-10-26 12:37   ` David Lazar
2023-10-29 13:30   ` David Lazar [this message]
2023-10-29 14:11     ` Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2023-10-29 18:20 David Lazar
2023-10-30  6:16 ` Greg KH
2023-10-30  7:36   ` David Lazar

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=ZT5ekV2JaWhf5bWF@localhost \
    --to=dlazar@gmail.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=markgross@kernel.org \
    --cc=mpearson-lenovo@squebb.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.