From: Greg KH <gregkh@linuxfoundation.org>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, jarredwhite@linux.microsoft.com,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: FAILED: Patch "ACPI: CPPC: Use access_width over bit_width for system memory accesses" failed to apply to 5.15-stable tree
Date: Fri, 29 Mar 2024 11:25:46 +0100 [thread overview]
Message-ID: <2024032936-bootleg-debtless-1975@gregkh> (raw)
In-Reply-To: <b34308af-ebc9-4a0e-a27b-90d6e176c526@linux.microsoft.com>
On Wed, Mar 27, 2024 at 08:48:17AM -0700, Easwar Hariharan wrote:
> Hi Sasha,
>
> On 3/27/2024 5:17 AM, Sasha Levin wrote:
> > The patch below does not apply to the 5.15-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > Thanks,
> > Sasha
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> >>>From 2f4a4d63a193be6fd530d180bb13c3592052904c Mon Sep 17 00:00:00 2001
> > From: Jarred White <jarredwhite@linux.microsoft.com>
> > Date: Fri, 1 Mar 2024 11:25:59 -0800
> > Subject: [PATCH] ACPI: CPPC: Use access_width over bit_width for system memory
> > accesses
> >
> > To align with ACPI 6.3+, since bit_width can be any 8-bit value, it
> > cannot be depended on to be always on a clean 8b boundary. This was
> > uncovered on the Cobalt 100 platform.
> >
>
> Please see the backport for this patch I sent earlier: https://lore.kernel.org/stable/6df99ad6-0402-4dcf-9a1c-7259436768dd@linux.microsoft.com/T/#u
Got it, now queued up, thanks!
greg k-h
prev parent reply other threads:[~2024-03-29 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 12:17 FAILED: Patch "ACPI: CPPC: Use access_width over bit_width for system memory accesses" failed to apply to 5.15-stable tree Sasha Levin
2024-03-27 15:48 ` Easwar Hariharan
2024-03-29 10:25 ` 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=2024032936-bootleg-debtless-1975@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=eahariha@linux.microsoft.com \
--cc=jarredwhite@linux.microsoft.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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 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.