From: Sasha Levin <sashal@kernel.org>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Jarred White <jarredwhite@linux.microsoft.com>
Subject: Re: [PATCH 5.15.y] ACPI: CPPC: Use access_width over bit_width for system memory accesses
Date: Wed, 20 Mar 2024 11:40:08 -0400 [thread overview]
Message-ID: <ZfsDWPWr2FIz6eX4@sashalap> (raw)
In-Reply-To: <6df99ad6-0402-4dcf-9a1c-7259436768dd@linux.microsoft.com>
On Tue, Mar 19, 2024 at 09:38:03AM -0700, Easwar Hariharan wrote:
>Hi Greg, Sasha,
>
>commit 2f4a4d63a193be6fd530d180bb13c3592052904c upstream is marked for 5.15+ with CC: stable@vger.kernel.org, but the
>application will fail with a merge conflict due to missing intermediate feature patches. When you apply the patch to 5.15,
>could you take the backport below instead?
Hey Easwar,
Thanks for the early heads-up, but we can only take it after it's been
in a released version (which should happen next week).
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-03-20 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 16:38 [PATCH 5.15.y] ACPI: CPPC: Use access_width over bit_width for system memory accesses Easwar Hariharan
2024-03-20 15:40 ` Sasha Levin [this message]
2024-03-20 17:30 ` Easwar Hariharan
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=ZfsDWPWr2FIz6eX4@sashalap \
--to=sashal@kernel.org \
--cc=eahariha@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarredwhite@linux.microsoft.com \
--cc=rafael@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