summaryrefslogtreecommitdiff
path: root/Documentation/block
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2023-03-15 21:39:05 +0300
committerJens Axboe <axboe@kernel.dk>2023-03-16 18:35:09 +0300
commit435c0e999689b7f383d0a27978cdaa08669cf134 (patch)
tree9747240fcfac504a6f80abcfcf2a1974189e9f73 /Documentation/block
parent5c7cb94452901a93e90c2230632e2c12a681bc92 (diff)
downloadlinux-435c0e999689b7f383d0a27978cdaa08669cf134.tar.xz
blk-crypto: remove blk_crypto_insert_cloned_request()
blk_crypto_insert_cloned_request() is the same as blk_crypto_rq_get_keyslot(), so just use that directly. Signed-off-by: Eric Biggers <ebiggers@google.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Link: https://lore.kernel.org/r/20230315183907.53675-2-ebiggers@kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'Documentation/block')
-rw-r--r--Documentation/block/inline-encryption.rst3
1 files changed, 1 insertions, 2 deletions
diff --git a/Documentation/block/inline-encryption.rst b/Documentation/block/inline-encryption.rst
index f9bf18ea6509..90b733422ed4 100644
--- a/Documentation/block/inline-encryption.rst
+++ b/Documentation/block/inline-encryption.rst
@@ -270,8 +270,7 @@ Request queue based layered devices like dm-rq that wish to support inline
encryption need to create their own blk_crypto_profile for their request_queue,
and expose whatever functionality they choose. When a layered device wants to
pass a clone of that request to another request_queue, blk-crypto will
-initialize and prepare the clone as necessary; see
-``blk_crypto_insert_cloned_request()``.
+initialize and prepare the clone as necessary.
Interaction between inline encryption and blk integrity
=======================================================