Re: FAILED: patch "[PATCH] rust: pin-init: replace shadowed return token by" failed to apply to 6.19-stable tree

[Greg KH <gregkh@linuxfoundation.org>]

On Mon, Mar 16, 2026 at 03:38:39PM +0100, Miguel Ojeda wrote:
> On Mon, Mar 16, 2026 at 3:34 PM <gregkh@linuxfoundation.org> wrote:
> >
> >
> > The patch below does not apply to the 6.19-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.19.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x fdbaa9d2b78e0da9e1aeb303bbdc3adfe6d8e749
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026031601-outrage-unheard-916c@gregkh' --subject-prefix 'PATCH 6.19.y' HEAD^..
> 
> This one and the other pin-init ones just sent were expected -- we
> will need a custom version, but we added Cc: stable@ to get the
> notification (if you prefer we avoid that, please let us know!):
> 
>   https://lore.kernel.org/all/CANiq72kk5_wzA9izJ3YPWUcQGiEUQmCif+iqFfwK9b_5mq145g@mail.gmail.com/

Nope, that's fine with me, treat our scripts as a trigger to backport
stuff :)