From: Greg KH <gregkh@linuxfoundation.org>
To: SG <prosparety@danwin1210.de>
Cc: stable@vger.kernel.org
Subject: Re: Request to add a patch to Stable Branch 6.1
Date: Thu, 17 Aug 2023 22:51:37 +0200 [thread overview]
Message-ID: <2023081712-flock-collapse-5cda@gregkh> (raw)
In-Reply-To: <bfd58918-d130-5b88-bd9e-39611fdbbfae@danwin1210.de>
On Thu, Aug 17, 2023 at 07:33:11PM -0000, SG wrote:
> (Before starting, i want to say i am not the developer of the patch, i am
> just an end user of a distribution kernel, which has just faced some
> problem, i don't even know if kernel team accepts patch requests from non
> dev, and thi mail is mostly shot in dark)
>
> Respected Sir/s/Ma'am/s
> I want to request that patch
> https://lore.kernel.org/all/20230627062442.54008-1-mika.westerberg@linux.intel.com/#r
> be accepted in to the stable 6.1 branch, it is already present in the
> current branch, and i request for it to be backported. This fixes some
> Intel CPUs (according to other users claims, ranging back to 6th gen
> for some) not going to deeper c states with kernels 5.16+, and was
> fixed by this patch in 6.4.4+, since many institutions, and
> distributions use 6.1, it would be great if this is included (from
> what i understand from requirements
> (https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html)
> i guess it fits all)
What is the git commit id of this change in Linus's tree?
thanks,
greg k-h
prev parent reply other threads:[~2023-08-17 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 19:33 Request to add a patch to Stable Branch 6.1 SG
2023-08-17 20:51 ` Greg KH [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=2023081712-flock-collapse-5cda@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=prosparety@danwin1210.de \
--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