From: Dan Williams <dan.j.williams@intel.com>
To: Eric Biggers <ebiggers@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
<linux-coco@lists.linux.dev>
Subject: Re: [PATCH] coco/guest: Remove unneeded selection of CRYPTO
Date: Sat, 14 Mar 2026 15:04:02 -0700 [thread overview]
Message-ID: <69b5db52e0aac_b2b6100b8@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20260314205533.GA45660@quark>
Eric Biggers wrote:
> On Thu, Jan 08, 2026 at 06:26:22PM -0800, Eric Biggers wrote:
> > On Wed, Dec 03, 2025 at 09:55:12PM -0800, Eric Biggers wrote:
> > > All that's needed here is CRYPTO_HASH_INFO. It used to be the case that
> > > CRYPTO_HASH_INFO was visible only when CRYPTO, but that was fixed by
> > > commit aacb37f597d0 ("lib/crypto: hash_info: Move hash_info.c into
> > > lib/crypto/"). Now CRYPTO_HASH_INFO can be selected directly.
> > >
> > > Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> > > ---
> > > drivers/virt/coco/guest/Kconfig | 1 -
> > > 1 file changed, 1 deletion(-)
> > >
> > > diff --git a/drivers/virt/coco/guest/Kconfig b/drivers/virt/coco/guest/Kconfig
> > > index 3d5e1d05bf34..da570dc4bd48 100644
> > > --- a/drivers/virt/coco/guest/Kconfig
> > > +++ b/drivers/virt/coco/guest/Kconfig
> > > @@ -11,7 +11,6 @@ config TSM_REPORTS
> > > tristate
> > >
> > > config TSM_MEASUREMENTS
> > > select TSM_GUEST
> > > select CRYPTO_HASH_INFO
> > > - select CRYPTO
> > > bool
> > >
> >
> > Any interest in applying this patch?
>
> Ping.
>
> If there continues to be no response, I'll take this patch via
> libcrypto-next.
Apologies, not sure how I missed this.
Acked-by: Dan Williams <dan.j.williams@intel.com>
...and yes, fine for this to go through libcrypto-next.
next prev parent reply other threads:[~2026-03-14 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 5:55 [PATCH] coco/guest: Remove unneeded selection of CRYPTO Eric Biggers
2026-01-09 2:26 ` Eric Biggers
2026-03-14 20:55 ` Eric Biggers
2026-03-14 22:04 ` Dan Williams [this message]
2026-03-15 17:15 ` Eric Biggers
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=69b5db52e0aac_b2b6100b8@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=ebiggers@kernel.org \
--cc=linux-coco@lists.linux.dev \
/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