public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Sasha Levin <sashal@kernel.org>
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 10:30:27 -0700	[thread overview]
Message-ID: <de88a013-8536-45c0-9344-5692fb3f0648@linux.microsoft.com> (raw)
In-Reply-To: <ZfsDWPWr2FIz6eX4@sashalap>

On 3/20/2024 8:40 AM, Sasha Levin wrote:
> 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 for the guidance on merge window policy, I just wasn't sure if I would get a "FAILED" email this week 
and thought I could be a bit proactive with the fix.

- Easwar

      reply	other threads:[~2024-03-20 17:30 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
2024-03-20 17:30   ` Easwar Hariharan [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=de88a013-8536-45c0-9344-5692fb3f0648@linux.microsoft.com \
    --to=eahariha@linux.microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarredwhite@linux.microsoft.com \
    --cc=rafael@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox