From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, "Theodore Y. Ts'o" <tytso@mit.edu>,
Mike Snitzer <snitzer@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-block@vger.kernel.org,
dm-devel@redhat.com, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [dm-devel] [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
Date: Tue, 15 Nov 2022 19:10:46 -0800 [thread overview]
Message-ID: <Y3RUtg9s+MeXi+Y1@sol.localdomain> (raw)
In-Reply-To: <20221114042944.1009870-2-hch@lst.de>
On Mon, Nov 14, 2022 at 05:29:42AM +0100, Christoph Hellwig wrote:
> Switch all public blk-crypto interfaces to use struct block_device
> arguments to specify the device they operate on instead of th
> request_queue, which is a block layer implementation detail.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@kernel.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces
Date: Tue, 15 Nov 2022 19:10:46 -0800 [thread overview]
Message-ID: <Y3RUtg9s+MeXi+Y1@sol.localdomain> (raw)
In-Reply-To: <20221114042944.1009870-2-hch@lst.de>
On Mon, Nov 14, 2022 at 05:29:42AM +0100, Christoph Hellwig wrote:
> Switch all public blk-crypto interfaces to use struct block_device
> arguments to specify the device they operate on instead of th
> request_queue, which is a block layer implementation detail.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2022-11-16 3:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 4:29 [dm-devel] pass a struct block_device to the blk-crypto interfaces v3 Christoph Hellwig
2022-11-14 4:29 ` Christoph Hellwig
2022-11-14 4:29 ` [dm-devel] [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces Christoph Hellwig
2022-11-14 4:29 ` Christoph Hellwig
2022-11-16 3:10 ` Eric Biggers [this message]
2022-11-16 3:10 ` Eric Biggers
2022-11-14 4:29 ` [dm-devel] [PATCH 2/3] blk-crypto: add a blk_crypto_config_supported_natively helper Christoph Hellwig
2022-11-14 4:29 ` Christoph Hellwig
2022-11-16 3:12 ` [dm-devel] " Eric Biggers
2022-11-16 3:12 ` Eric Biggers
2022-11-14 4:29 ` [dm-devel] [PATCH 3/3] blk-crypto: move internal only declarations to blk-crypto-internal.h Christoph Hellwig
2022-11-14 4:29 ` Christoph Hellwig
2022-11-14 10:45 ` [dm-devel] " kernel test robot
2022-11-14 10:45 ` kernel test robot
2022-11-14 11:25 ` [dm-devel] " kernel test robot
2022-11-14 11:25 ` kernel test robot
2022-11-15 9:06 ` [dm-devel] " Christoph Hellwig
2022-11-15 9:06 ` Christoph Hellwig
2022-11-16 3:18 ` Eric Biggers
2022-11-16 3:18 ` Eric Biggers
2022-11-21 18:39 ` [dm-devel] pass a struct block_device to the blk-crypto interfaces v3 Jens Axboe
2022-11-21 18:39 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-11-07 14:42 [dm-devel] pass a struct block_device to the blk-crypto interfaces v2 Christoph Hellwig
2022-11-07 14:42 ` [dm-devel] [PATCH 1/3] blk-crypto: don't use struct request_queue for public interfaces Christoph Hellwig
2022-11-07 20:16 ` Eric Biggers
2022-11-09 13:14 ` 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=Y3RUtg9s+MeXi+Y1@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=snitzer@kernel.org \
--cc=tytso@mit.edu \
/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.