From: Greg KH <gregkh@linuxfoundation.org>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: vanshikonda@os.amperecomputing.com,
jarredwhite@linux.microsoft.com, rafael.j.wysocki@intel.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ACPI: CPPC: Fix access width used for PCC registers" failed to apply to 5.15-stable tree
Date: Tue, 30 Apr 2024 20:27:43 +0200 [thread overview]
Message-ID: <2024043030-divinity-cube-9d5c@gregkh> (raw)
In-Reply-To: <3693107b-054d-485a-9e1c-c23c683db590@linux.microsoft.com>
On Tue, Apr 30, 2024 at 11:05:06AM -0700, Easwar Hariharan wrote:
> On 4/30/2024 10:41 AM, Greg KH wrote:
> > On Tue, Apr 30, 2024 at 09:05:28AM -0700, Easwar Hariharan wrote:
> >> On 4/29/2024 4:53 AM, gregkh@linuxfoundation.org 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>.
> >>>
> >>> To reproduce the conflict and resubmit, you may use the following commands:
> >>>
> >>> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.15.y
> >>> git checkout FETCH_HEAD
> >>> git cherry-pick -x f489c948028b69cea235d9c0de1cc10eeb26a172
> >>> # <resolve conflicts, build, test, etc.>
> >>> git commit -s
> >>> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2024042905-puppy-heritage-e422@gregkh' --subject-prefix 'PATCH 5.15.y' HEAD^..
> >>>
> >>> Possible dependencies:
> >>>
> >>> f489c948028b ("ACPI: CPPC: Fix access width used for PCC registers")
> >>> 2f4a4d63a193 ("ACPI: CPPC: Use access_width over bit_width for system memory accesses")
> >>> 0651ab90e4ad ("ACPI: CPPC: Check _OSC for flexible address space")
> >>> c42fa24b4475 ("ACPI: bus: Avoid using CPPC if not supported by firmware")
> >>> 2ca8e6285250 ("Revert "ACPI: Pass the same capabilities to the _OSC regardless of the query flag"")
> >>> f684b1075128 ("ACPI: CPPC: Drop redundant local variable from cpc_read()")
> >>> 5f51c7ce1dc3 ("ACPI: CPPC: Fix up I/O port access in cpc_read()")
> >>> a2c8f92bea5f ("ACPI: CPPC: Implement support for SystemIO registers")
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >>>
> >>
> >> Hi Greg,
> >>
> >> Please fix this with the following set of changes in linux-5.15.y.
> >>
> >> Revert b54c4632946ae42f2b39ed38abd909bbf78cbcc2 from linux-5.15.y
> >> Cherry-pick 05d92ee782eeb7b939bdd0189e6efcab9195bf95 from upstream
> >> Pick the following backport of f489c948028b69cea235d9c0de1cc10eeb26a172 from upstream
> >
> > Please provide a series of patches that I can apply that does this,
> > attempting to revert and cherry-pick and then manually hand-edit this
> > email and apply it does not scale at all, sorry.
> >
> > thanks,
> >
> > greg k-h
>
> Sorry about that, I'll send the series right away. I'm not quite sure what Closes: lore link to provide, could you please fix it up?
There's no need for any "Closes:" link for stable backports.
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-30 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 11:53 FAILED: patch "[PATCH] ACPI: CPPC: Fix access width used for PCC registers" failed to apply to 5.15-stable tree gregkh
2024-04-30 16:05 ` Easwar Hariharan
2024-04-30 17:41 ` Greg KH
2024-04-30 18:05 ` Easwar Hariharan
2024-04-30 18:27 ` Greg KH [this message]
2024-04-30 18:09 ` [PATCH 5.15.y 1/3] Revert "Revert "ACPI: CPPC: Use access_width over bit_width for system memory accesses"" Easwar Hariharan
2024-04-30 18:09 ` [PATCH 5.15.y 2/3] ACPI: CPPC: Fix bit_offset shift in MASK_VAL() macro Easwar Hariharan
2024-04-30 18:09 ` [PATCH 5.15.y 3/3] ACPI: CPPC: Fix access width used for PCC registers 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=2024043030-divinity-cube-9d5c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=eahariha@linux.microsoft.com \
--cc=jarredwhite@linux.microsoft.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=vanshikonda@os.amperecomputing.com \
/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 NNTP newsgroup(s).