From: Greg KH <gregkh@linuxfoundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: phx0fer@gmail.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] crypto: krb5enc - fix async decrypt skipping hash" failed to apply to 7.0-stable tree
Date: Thu, 23 Apr 2026 08:07:45 +0200 [thread overview]
Message-ID: <2026042340-entail-elite-34f8@gregkh> (raw)
In-Reply-To: <aemwlWqIUk5WR413@gondor.apana.org.au>
On Thu, Apr 23, 2026 at 01:39:33PM +0800, Herbert Xu wrote:
> On Thu, Apr 23, 2026 at 07:04:55AM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 7.0-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-7.0.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 3bfbf5f0a99c991769ec562721285df7ab69240b
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026042355-fructose-married-6872@gregkh' --subject-prefix 'PATCH 7.0.y' HEAD^..
> >
> > Possible dependencies:
>
> It should apply if you first bring in
>
> commit 2ef3bac16fb5e9eee4fb1d722578a79b751ea58a
> Author: Wesley Atwell <atwellwea@gmail.com>
> Date: Mon Mar 9 00:26:24 2026 -0600
>
> crypto: krb5enc - fix sleepable flag handling in encrypt dispatch
That worked, thanks!
greg k-h
prev parent reply other threads:[~2026-04-23 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 5:04 FAILED: patch "[PATCH] crypto: krb5enc - fix async decrypt skipping hash" failed to apply to 7.0-stable tree gregkh
2026-04-23 5:39 ` Herbert Xu
2026-04-23 6:07 ` Greg KH [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=2026042340-entail-elite-34f8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=phx0fer@gmail.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