Stable Archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH RESEND 5.15.y 0/3] Use access_width for _CPC package when provided by the platform firmware
Date: Sat, 11 May 2024 09:25:22 -0400	[thread overview]
Message-ID: <Zj9xwkZmWT7SC5cv@sashalap> (raw)
In-Reply-To: <20240509194126.3020424-1-eahariha@linux.microsoft.com>

On Thu, May 09, 2024 at 07:41:23PM +0000, Easwar Hariharan wrote:
>This series backports the original patch[1] and fixes to it[2][3], all marked for
>stable, that fix a kernel panic when using the wrong access size when
>platform firmware provides the access size to use for the _CPC ACPI
>package.
>
>This series was originally sent in response to an automated email
>notifying authors, reviewers, and maintainer of a failure to apply patch
>[3] to linux-5.15.y at [4].

Queued up, thanks!

-- 
Thanks,
Sasha

      parent reply	other threads:[~2024-05-11 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 19:41 [PATCH RESEND 5.15.y 0/3] Use access_width for _CPC package when provided by the platform firmware Easwar Hariharan
2024-05-09 19:41 ` [PATCH RESEND 5.15.y 1/3] Revert "Revert "ACPI: CPPC: Use access_width over bit_width for system memory accesses"" Easwar Hariharan
2024-05-09 19:41 ` [PATCH RESEND 5.15.y 2/3] ACPI: CPPC: Fix bit_offset shift in MASK_VAL() macro Easwar Hariharan
2024-05-09 19:41 ` [PATCH RESEND 5.15.y 3/3] ACPI: CPPC: Fix access width used for PCC registers Easwar Hariharan
2024-05-11 13:25 ` Sasha Levin [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=Zj9xwkZmWT7SC5cv@sashalap \
    --to=sashal@kernel.org \
    --cc=eahariha@linux.microsoft.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).