From: Greg KH <gregkh@linuxfoundation.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: stable@vger.kernel.org, herbert@gondor.apana.org.au,
thomas.lendacky@amd.com, Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH stable-5.4] crypto: ccp - Annotate SEV Firmware file names
Date: Thu, 15 Jul 2021 12:50:53 +0200 [thread overview]
Message-ID: <YPATDUsDzIb1iote@kroah.com> (raw)
In-Reply-To: <20210712121250.23392-1-joro@8bytes.org>
On Mon, Jul 12, 2021 at 02:12:50PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> [ Upstream commit c8671c7dc7d51125ab9f651697866bf4a9132277 ]
>
> Annotate the firmware files CCP might need using MODULE_FIRMWARE().
> This will get them included into an initrd when CCP is also included
> there. Otherwise the CCP module will not find its firmware when loaded
> before the root-fs is mounted.
> This can cause problems when the pre-loaded SEV firmware is too old to
> support current SEV and SEV-ES virtualization features.
>
> Fixes: e93720606efd ("crypto: ccp - Allow SEV firmware to be chosen based on Family and Model")
> Cc: stable@vger.kernel.org # v4.20+
> Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> ---
> drivers/crypto/ccp/psp-dev.c | 4 ++++
> 1 file changed, 4 insertions(+)
Now applied, thanks!
greg k-h
prev parent reply other threads:[~2021-07-15 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 12:17 FAILED: patch "[PATCH] crypto: ccp - Annotate SEV Firmware file names" failed to apply to 5.4-stable tree gregkh
2021-07-12 12:12 ` [PATCH stable-5.4] crypto: ccp - Annotate SEV Firmware file names Joerg Roedel
2021-07-15 10:50 ` 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=YPATDUsDzIb1iote@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--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 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.