From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/3] blk-crypto: pass a gendisk to blk_crypto_sysfs_register
Date: Mon, 7 Nov 2022 11:55:24 -0800 [thread overview]
Message-ID: <Y2lirLd1Gxs6+HEd@sol.localdomain> (raw)
In-Reply-To: <20221105080815.775721-1-hch@lst.de>
On Sat, Nov 05, 2022 at 09:08:13AM +0100, Christoph Hellwig wrote:
> Prepare for changes to the block layer sysfs handling by passing the
> readily available gendisk to blk_crypto_sysfs_register.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-crypto-internal.h | 4 ++--
> block/blk-crypto-sysfs.c | 3 ++-
> block/blk-sysfs.c | 2 +-
> 3 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/block/blk-crypto-internal.h b/block/blk-crypto-internal.h
> index e6818ffaddbf8..32990299dace1 100644
> --- a/block/blk-crypto-internal.h
> +++ b/block/blk-crypto-internal.h
> @@ -21,7 +21,7 @@ extern const struct blk_crypto_mode blk_crypto_modes[];
>
> #ifdef CONFIG_BLK_INLINE_ENCRYPTION
>
> -int blk_crypto_sysfs_register(struct request_queue *q);
> +int blk_crypto_sysfs_register(struct gendisk *disk);
>
> void blk_crypto_sysfs_unregister(struct request_queue *q);
Shouldn't blk_crypto_sysfs_unregister() be updated to match?
- Eric
next prev parent reply other threads:[~2022-11-07 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 8:08 [PATCH 1/3] blk-crypto: pass a gendisk to blk_crypto_sysfs_register Christoph Hellwig
2022-11-05 8:08 ` [PATCH 2/3] block: untangle request_queue refcounting from sysfs Christoph Hellwig
2022-11-07 19:57 ` Eric Biggers
2022-11-09 13:01 ` Christoph Hellwig
2022-11-05 8:08 ` [PATCH 3/3] block: mark blk_put_queue as potentially blocking Christoph Hellwig
2022-11-07 19:55 ` Eric Biggers [this message]
2022-11-09 12:49 ` [PATCH 1/3] blk-crypto: pass a gendisk to blk_crypto_sysfs_register Christoph Hellwig
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=Y2lirLd1Gxs6+HEd@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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