From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/5] blk-crypto: pass a gendisk to blk_crypto_sysfs_{,un}register
Date: Thu, 17 Nov 2022 18:59:32 -0800 [thread overview]
Message-ID: <Y3b1FDhjTQ+JFiBB@sol.localdomain> (raw)
In-Reply-To: <20221114042637.1009333-2-hch@lst.de>
On Mon, Nov 14, 2022 at 05:26:33AM +0100, Christoph Hellwig wrote:
> Prepare for changes to the block layer sysfs handling by passing the
> readily available gendisk to blk_crypto_sysfs_{,un}register.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-crypto-internal.h | 10 ++++++----
> block/blk-crypto-sysfs.c | 7 ++++---
> block/blk-sysfs.c | 4 ++--
> 3 files changed, 12 insertions(+), 9 deletions(-)
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2022-11-18 2:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 4:26 untangle the request_queue refcounting from the queue kobject v2 Christoph Hellwig
2022-11-14 4:26 ` [PATCH 1/5] blk-crypto: pass a gendisk to blk_crypto_sysfs_{,un}register Christoph Hellwig
2022-11-18 2:59 ` Eric Biggers [this message]
2022-11-14 4:26 ` [PATCH 2/5] block: factor out a blk_debugfs_remove helper Christoph Hellwig
2022-11-14 4:26 ` [PATCH 3/5] block: fix error unwinding in blk_register_queue Christoph Hellwig
2022-11-14 4:26 ` [PATCH 4/5] block: untangle request_queue refcounting from sysfs Christoph Hellwig
2022-11-14 4:26 ` [PATCH 5/5] block: mark blk_put_queue as potentially blocking Christoph Hellwig
2022-11-19 2:19 ` untangle the request_queue refcounting from the queue kobject v2 Al Viro
2022-11-19 3:00 ` Al Viro
2022-11-21 7:03 ` Christoph Hellwig
2022-11-21 7:02 ` Christoph Hellwig
2022-11-21 8:27 ` Christoph Hellwig
2022-11-30 18:09 ` Jens Axboe
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=Y3b1FDhjTQ+JFiBB@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;
as well as URLs for NNTP newsgroup(s).