summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-10-04 06:18:34 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2022-10-04 06:18:34 +0300
commit438b2cdd17a6c9df607f574bd13b6b637795a411 (patch)
treeb601504eb8a1808eb93391772b4f946095b4a5ea /tools/perf/scripts/python/export-to-postgresql.py
parentf4309528f3dec3ead08cd4bd09e0e5fe081ab9f9 (diff)
parent0e91fc1e0f5c70ce575451103ec66c2ec21f1a6e (diff)
downloadlinux-438b2cdd17a6c9df607f574bd13b6b637795a411.tar.xz
Merge tag 'fscrypt-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt
Pull fscrypt updates from Eric Biggers: "This release contains some implementation changes, but no new features: - Rework the implementation of the fscrypt filesystem-level keyring to not be as tightly coupled to the keyrings subsystem. This resolves several issues. - Eliminate most direct uses of struct request_queue from fs/crypto/, since struct request_queue is considered to be a block layer implementation detail. - Stop using the PG_error flag to track decryption failures. This is a prerequisite for freeing up PG_error for other uses" * tag 'fscrypt-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt: fscrypt: work on block_devices instead of request_queues fscrypt: stop holding extra request_queue references fscrypt: stop using keyrings subsystem for fscrypt_master_key fscrypt: stop using PG_error to track error status fscrypt: remove fscrypt_set_test_dummy_encryption()
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions