summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2025-02-17 21:51:05 +0300
committerEric Biggers <ebiggers@google.com>2025-02-17 22:34:15 +0300
commita19bcde49998aac0a4ff99e9a84339adecffbfcb (patch)
tree456d0a28548bb3a50f1f30eda45ab0df73c9a120 /tools/perf/scripts/python/export-to-postgresql.py
parent212df80e01069da2a179e6ab28c3f52c325575e1 (diff)
downloadlinux-a19bcde49998aac0a4ff99e9a84339adecffbfcb.tar.xz
Revert "fsverity: relax build time dependency on CRYPTO_SHA256"
This reverts commit e3a606f2c544b231f6079c8c5fea451e772e1139 because it allows people to create broken configurations that enable FS_VERITY but not SHA-256 support. The commit did allow people to disable the generic SHA-256 implementation when it's not needed. But that at best allowed saving a bit of code. In the real world people are unlikely to intentionally and correctly make such a tweak anyway, as they tend to just be confused by what all the different crypto kconfig options mean. Of course we really need the crypto API to enable the correct implementations automatically, but that's for a later fix. Acked-by: Ard Biesheuvel <ardb@kernel.org> Cc: Herbert Xu <herbert@gondor.apana.org.au> Link: https://lore.kernel.org/r/20250217185105.26751-1-ebiggers@kernel.org Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions