From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-block@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
Bart Van Assche <bvanassche@acm.org>,
Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 6.1 4/7] blk-crypto: Add a missing include directive
Date: Wed, 3 May 2023 20:54:14 -0700 [thread overview]
Message-ID: <20230504035417.61435-5-ebiggers@kernel.org> (raw)
In-Reply-To: <20230504035417.61435-1-ebiggers@kernel.org>
From: Bart Van Assche <bvanassche@acm.org>
commit 85168d416e5d3184b77dbec8fee75c9439894afa upstream.
Allow the compiler to verify consistency of function declarations and
function definitions. This patch fixes the following sparse errors:
block/blk-crypto-profile.c:241:14: error: no previous prototype for ‘blk_crypto_get_keyslot’ [-Werror=missing-prototypes]
241 | blk_status_t blk_crypto_get_keyslot(struct blk_crypto_profile *profile,
| ^~~~~~~~~~~~~~~~~~~~~~
block/blk-crypto-profile.c:318:6: error: no previous prototype for ‘blk_crypto_put_keyslot’ [-Werror=missing-prototypes]
318 | void blk_crypto_put_keyslot(struct blk_crypto_keyslot *slot)
| ^~~~~~~~~~~~~~~~~~~~~~
block/blk-crypto-profile.c:344:6: error: no previous prototype for ‘__blk_crypto_cfg_supported’ [-Werror=missing-prototypes]
344 | bool __blk_crypto_cfg_supported(struct blk_crypto_profile *profile,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
block/blk-crypto-profile.c:373:5: error: no previous prototype for ‘__blk_crypto_evict_key’ [-Werror=missing-prototypes]
373 | int __blk_crypto_evict_key(struct blk_crypto_profile *profile,
| ^~~~~~~~~~~~~~~~~~~~~~
Cc: Eric Biggers <ebiggers@google.com>
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Link: https://lore.kernel.org/r/20221123172923.434339-1-bvanassche@acm.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
block/blk-crypto-profile.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/blk-crypto-profile.c b/block/blk-crypto-profile.c
index 96c511967386d..0307fb0d95d34 100644
--- a/block/blk-crypto-profile.c
+++ b/block/blk-crypto-profile.c
@@ -32,6 +32,7 @@
#include <linux/wait.h>
#include <linux/blkdev.h>
#include <linux/blk-integrity.h>
+#include "blk-crypto-internal.h"
struct blk_crypto_keyslot {
atomic_t slot_refs;
--
2.40.1
next prev parent reply other threads:[~2023-05-04 3:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 3:54 [PATCH 6.1 0/7] blk-crypto fixes for 6.1 Eric Biggers
2023-05-04 3:54 ` [PATCH 6.1 1/7] blk-crypto: don't use struct request_queue for public interfaces Eric Biggers
2023-05-04 3:54 ` [PATCH 6.1 2/7] blk-crypto: add a blk_crypto_config_supported_natively helper Eric Biggers
2023-05-04 3:54 ` [PATCH 6.1 3/7] blk-crypto: move internal only declarations to blk-crypto-internal.h Eric Biggers
2023-05-04 3:54 ` Eric Biggers [this message]
2023-05-04 3:54 ` [PATCH 6.1 5/7] blk-mq: release crypto keyslot before reporting I/O complete Eric Biggers
2023-05-04 3:54 ` [PATCH 6.1 6/7] blk-crypto: make blk_crypto_evict_key() return void Eric Biggers
2023-05-04 3:54 ` [PATCH 6.1 7/7] blk-crypto: make blk_crypto_evict_key() more robust Eric Biggers
2023-05-06 2:06 ` [PATCH 6.1 0/7] blk-crypto fixes for 6.1 Greg KH
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=20230504035417.61435-5-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=ebiggers@google.com \
--cc=linux-block@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.