From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@google.com>
Cc: herbert@gondor.apana.org.au, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] crypto: gcm - fix incompatibility between "gcm" and" failed to apply to 4.9-stable tree
Date: Sat, 18 May 2019 08:56:36 +0200 [thread overview]
Message-ID: <20190518065636.GC28796@kroah.com> (raw)
In-Reply-To: <20190517174025.GB223128@google.com>
On Fri, May 17, 2019 at 10:40:25AM -0700, Eric Biggers wrote:
> On Fri, May 17, 2019 at 02:37:18PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.9-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>.
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > From f699594d436960160f6d5ba84ed4a222f20d11cd Mon Sep 17 00:00:00 2001
> > From: Eric Biggers <ebiggers@google.com>
> > Date: Thu, 18 Apr 2019 14:43:02 -0700
> > Subject: [PATCH] crypto: gcm - fix incompatibility between "gcm" and
> > "gcm_base"
> >
>
> Can you apply the following commit first? Then this one applies cleanly:
>
> commit 9b40f79c08e81234d759f188b233980d7e81df6c
> Author: Wei Yongjun <weiyongjun1@huawei.com>
> Date: Mon Oct 17 15:10:06 2016 +0000
>
> crypto: gcm - Fix error return code in crypto_gcm_create_common()
Thank you, that worked!
greg k-h
prev parent reply other threads:[~2019-05-18 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 12:37 FAILED: patch "[PATCH] crypto: gcm - fix incompatibility between "gcm" and" failed to apply to 4.9-stable tree gregkh
2019-05-17 17:40 ` Eric Biggers
2019-05-18 6:56 ` 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=20190518065636.GC28796@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--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;
as well as URLs for NNTP newsgroup(s).