From: Eric Biggers <ebiggers@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] bcachefs: Explicitly select CRYPTO from BCACHEFS_FS
Date: Wed, 23 Oct 2024 19:00:38 +0000 [thread overview]
Message-ID: <20241023190038.GA3736641@google.com> (raw)
In-Reply-To: <3jhkejzn2prqk5xmqudfo4czy6fgxivqbcxkg7vq42x7z77lte@zwh6glvjgoiw>
On Wed, Oct 23, 2024 at 02:49:38PM -0400, Kent Overstreet wrote:
> On Wed, Oct 23, 2024 at 06:35:21PM +0000, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Explicitly select CRYPTO from BCACHEFS_FS, so that this dependency of
> > CRYPTO_SHA256, CRYPTO_CHACHA20, and CRYPTO_POLY1305 (which are also
> > selected) is satisfied. Currently this dependency is satisfied
> > indirectly via LIBCRC32C, but this is fragile and is planned to change
> > (https://lore.kernel.org/r/20241021002935.325878-13-ebiggers@kernel.org).
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202410232254.ogS6Em2d-lkp@intel.com/
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Thanks, applied
>
> (or acked-by, if you want to take it through your tree?)
Please go ahead and take it. It will take a while to get my patchset merged,
and it will help to get dependencies like this out of the way first. Thanks!
- Eric
prev parent reply other threads:[~2024-10-23 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 18:35 [PATCH] bcachefs: Explicitly select CRYPTO from BCACHEFS_FS Eric Biggers
2024-10-23 18:49 ` Kent Overstreet
2024-10-23 19:00 ` Eric Biggers [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=20241023190038.GA3736641@google.com \
--to=ebiggers@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=lkp@intel.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