On Mon, Jul 29, 2024 at 10:20:03AM +0200, Greg Kroah-Hartman wrote: > On Mon, Jul 29, 2024 at 09:10:54AM +0100, Marc Zyngier wrote: > > On Mon, 29 Jul 2024 08:51:16 +0100, > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > The patch below does not apply to the 6.10-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@xxxxxxxxxxxxxxx>. > > > > > > 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-6.10.y > > > git checkout FETCH_HEAD > > > git cherry-pick -x 080402007007ca1bed8bcb103625137a5c8446c6 > > > # <resolve conflicts, build, test, etc.> > > > git commit -s > > > git send-email --to '<stable@xxxxxxxxxxxxxxx>' --in-reply-to '2024072916-brewing-cavalier-a90a@gregkh' --subject-prefix 'PATCH 6.10.y' HEAD^.. > > > > > > Possible dependencies: > > > > > > 080402007007 ("irqchip/gic-v3: Fix 'broken_rdists' unused warning when !SMP and !ACPI") > > > d633da5d3ab1 ("irqchip/gic-v3: Add support for ACPI's disabled but 'online capable' CPUs") > > > fa2dabe57220 ("irqchip/gic-v3: Don't return errors from gic_acpi_match_gicc()") > > > > None of these three patches should be stable candidate for 6.10. They > > only matter to CPU hotplug, which is a new feature for 6.11 and has > > no purpose being backported. > > That's fine, thanks, it was odd that this commit was tagged for stable > inclusion at all... Ah, sorry, my script for generating the Fixes line inserted a cc stable and I missed it. It should have only had the Fixes tag for something that went in 6.11, no backports. -- Catalin
