mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>,
	stable@vger.kernel.org, Brijesh Singh <brijesh.singh@amd.com>,
	Paul Gazzillo <paul@pgazz.com>,
	Necip Fazil Yildiran <fazilyildiran@gmail.com>,
	Borislav Petkov <bp@suse.de>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH] virt: sev-guest: fix kconfig warnings
Date: Wed, 2 Nov 2022 23:23:10 -0700	[thread overview]
Message-ID: <ccefc0b7-528d-32a5-328c-e166b4821f76@infradead.org> (raw)
In-Reply-To: <20220828195234.6604-1-rdunlap@infradead.org>

ping. I have verified (on linux-next-20221103) that this
patch is still needed.
Thanks.

On 8/28/22 12:52, Randy Dunlap wrote:
> Fix the SEV_GUEST Kconfig block to eliminate kconfig unmet
> dependency warnings:
> 
> WARNING: unmet direct dependencies detected for CRYPTO_GCM
>   Depends on [n]: CRYPTO [=n]
>   Selected by [y]:
>   - SEV_GUEST [=y] && VIRT_DRIVERS [=y] && AMD_MEM_ENCRYPT [=y]
> 
> WARNING: unmet direct dependencies detected for CRYPTO_AEAD2
>   Depends on [n]: CRYPTO [=n]
>   Selected by [y]:
>   - SEV_GUEST [=y] && VIRT_DRIVERS [=y] && AMD_MEM_ENCRYPT [=y]
> 
> Fixes: fce96cf04430 ("virt: Add SEV-SNP guest driver")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: stable@vger.kernel.org
> Cc: Brijesh Singh <brijesh.singh@amd.com>
> Cc: Paul Gazzillo <paul@pgazz.com>
> Cc: Necip Fazil Yildiran <fazilyildiran@gmail.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: linux-crypto@vger.kernel.org
> ---
>  drivers/virt/coco/sev-guest/Kconfig |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- a/drivers/virt/coco/sev-guest/Kconfig
> +++ b/drivers/virt/coco/sev-guest/Kconfig
> @@ -2,6 +2,7 @@ config SEV_GUEST
>  	tristate "AMD SEV Guest driver"
>  	default m
>  	depends on AMD_MEM_ENCRYPT
> +	select CRYPTO
>  	select CRYPTO_AEAD2
>  	select CRYPTO_GCM
>  	help

-- 
~Randy

  reply	other threads:[~2022-11-03  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 19:52 Randy Dunlap
2022-11-03  6:23 ` Randy Dunlap [this message]
2023-05-29 23:13 Randy Dunlap

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=ccefc0b7-528d-32a5-328c-e166b4821f76@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bp@suse.de \
    --cc=brijesh.singh@amd.com \
    --cc=fazilyildiran@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=paul@pgazz.com \
    --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

all inboxes | Powered by JetHome®