linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Allen <john.allen@amd.com>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-crypto@vger.kernel.org, thomas.lendacky@amd.com,
	herbert@gondor.apana.org.au, stable@vger.kernel.org
Subject: Re: [PATCH] crypto: ccp - Fix use of merged scatterlists
Date: Thu, 25 Jun 2020 13:21:13 -0500	[thread overview]
Message-ID: <20200625182113.GA733263@mojo.amd.com> (raw)
In-Reply-To: <20200625145356.4377E20781@mail.kernel.org>

On Thu, Jun 25, 2020 at 02:53:55PM +0000, Sasha Levin wrote:
> Hi
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: 63b945091a07 ("crypto: ccp - CCP device driver and interface support").
> 
> The bot has tested the following trees: v5.7.5, v5.4.48, v4.19.129, v4.14.185, v4.9.228, v4.4.228.
> 
> v5.7.5: Build OK!
> v5.4.48: Build OK!
> v4.19.129: Build OK!
> v4.14.185: Build OK!
> v4.9.228: Build OK!
> v4.4.228: Failed to apply! Possible dependencies:
>     3f19ce2054541 ("crypto: ccp - Remove check for x86 family and model")
>     553d2374db0bb ("crypto: ccp - Support for multiple CCPs")
>     c7019c4d739e7 ("crypto: ccp - CCP versioning support")
>     ea0375afa1728 ("crypto: ccp - Add abstraction for device-specific calls")
> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?

Please apply this patch to v4.9.x and newer.

Thanks,
John

> 
> -- 
> Thanks
> Sasha

  reply	other threads:[~2020-06-25 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 20:24 [PATCH] crypto: ccp - Fix use of merged scatterlists John Allen
2020-06-24 20:19 ` Tom Lendacky
2020-06-25 14:53 ` Sasha Levin
2020-06-25 18:21   ` John Allen [this message]
2020-07-03  4:48 ` Herbert Xu

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=20200625182113.GA733263@mojo.amd.com \
    --to=john.allen@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=thomas.lendacky@amd.com \
    /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).