linux-kernel - Re: [PATCH] platform/x86: Add s2idle quirk for more Lenovo laptops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7eb734c7-1246-d938-49da-fb1419d35492@redhat.com>
Date:   Sun, 29 Oct 2023 15:11:33 +0100
From:   Hans de Goede <hdegoede@...hat.com>
To:     David Lazar <dlazar@...il.com>
Cc:     Shyam Sundar S K <Shyam-sundar.S-k@....com>,
        Mark Gross <markgross@...nel.org>,
        platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
        Mario Limonciello <mario.limonciello@....com>,
        Mark Pearson <mpearson-lenovo@...ebb.ca>
Subject: Re: [PATCH] platform/x86: Add s2idle quirk for more Lenovo laptops

Hi David,

On 10/29/23 14:30, David Lazar wrote:
> 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@...r.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?

Yes you should also submit the patch to the stable series.

To do this send the patch to stable@...r.kernel.org and at the top
of the body (so below the first line / subject) of the commit msg add:

commit 3bde7ec13c971445faade32172cb0b4370b841d9 upstream

So the entire commit msg should look like this:

"""
<original subject>

commit 3bde7ec13c971445faade32172cb0b4370b841d9 upstream

<original
 body>
"""

And then submit the patch with this updated subject to
stable@...r.kernel.org and that's it.

Regards,

Hans