From: Catalin Marinas <catalin.marinas@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Marc Zyngier <maz@kernel.org>, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] irqchip/gic-v3: Fix 'broken_rdists' unused warning when !SMP" failed to apply to 6.10-stable tree
Date: Mon, 29 Jul 2024 10:55:02 +0100 [thread overview]
Message-ID: <Zqdm9lQaL_ikpTgY@arm.com> (raw)
In-Reply-To: <2024072946-charbroil-emporium-ca54@gregkh>
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@linuxfoundation.org> 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@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-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@vger.kernel.org>' --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
prev parent reply other threads:[~2024-07-29 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 7:51 FAILED: patch "[PATCH] irqchip/gic-v3: Fix 'broken_rdists' unused warning when !SMP" failed to apply to 6.10-stable tree gregkh
2024-07-29 8:10 ` Marc Zyngier
2024-07-29 8:20 ` Greg KH
2024-07-29 9:55 ` Catalin Marinas [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=Zqdm9lQaL_ikpTgY@arm.com \
--to=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=maz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.