linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	"Jason A . Donenfeld " <Jason@zx2c4.com>
Subject: [PATCH 0/2] crypto: make the sha1 library optional
Date: Sat,  9 Jul 2022 14:18:47 -0700	[thread overview]
Message-ID: <20220709211849.210850-1-ebiggers@kernel.org> (raw)

This series makes it possible to build the kernel without SHA-1 support,
although for now this is only possible in minimal configurations, due to
the uses of SHA-1 in the networking subsystem.

Eric Biggers (2):
  crypto: move lib/sha1.c into lib/crypto/
  crypto: make the sha1 library optional

 crypto/Kconfig          | 1 +
 init/Kconfig            | 1 +
 lib/Makefile            | 2 +-
 lib/crypto/Kconfig      | 3 +++
 lib/crypto/Makefile     | 3 +++
 lib/{ => crypto}/sha1.c | 0
 net/ipv6/Kconfig        | 1 +
 7 files changed, 10 insertions(+), 1 deletion(-)
 rename lib/{ => crypto}/sha1.c (100%)


base-commit: 79e6e2f3f3ff345947075341781e900e4f70db81
-- 
2.37.0


             reply	other threads:[~2022-07-09 21:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 21:18 Eric Biggers [this message]
2022-07-09 21:18 ` [PATCH 1/2] crypto: move lib/sha1.c into lib/crypto/ Eric Biggers
2022-07-11 14:58   ` Jason A. Donenfeld
2022-07-09 21:18 ` [PATCH 2/2] crypto: make the sha1 library optional Eric Biggers
2022-07-11 14:59   ` Jason A. Donenfeld
2022-07-11 18:03   ` Jakub Kicinski
2022-07-15  1:18     ` Alexei Starovoitov
2022-07-15  8:50 ` [PATCH 0/2] " Herbert Xu
2022-07-18 17:49   ` Randy Dunlap
2022-07-19  3:48     ` 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=20220709211849.210850-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).