Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Eric Biggers <ebiggers@xxxxxxxxxx>
Subject: Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 4 Nov 2022 08:32:16 +0100
In-reply-to: <Y2S/DfZTr90t6QXv@sol.localdomain>
References: <20221104054621.628369-1-hch@lst.de> <20221104054621.628369-2-hch@lst.de> <Y2S/DfZTr90t6QXv@sol.localdomain>
User-agent: Mutt/1.5.17 (2007-11-01)

On Fri, Nov 04, 2022 at 12:28:13AM -0700, Eric Biggers wrote:
> Shouldn't the three places above still say request_queue, not block_device?
> They're talking about the driver.

Yes, probably.

References:
- pass a struct block_device to the blk-crypto interfaces
  - From: Christoph Hellwig
- [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
  - From: Christoph Hellwig
- Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
  - From: Eric Biggers

Prev by Date: Re: [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
Next by Date: [xfstests PATCH v2 1/3] common/verity: fix _fsv_have_hash_algorithm() with required signatures
Previous by thread: Re: [PATCH 1/2] blk-crypto: don't use struct request_queue for public interfaces
Next by thread: [PATCH 2/2] blk-crypto: add a blk_crypto_cfg_supported helper
Index(es):
- Date
- Thread

[Index of Archives] [linux Cryptography] [Asterisk App Development] [PJ SIP] [Gnu Gatekeeper] [IETF Sipping] [Info Cyrus] [ALSA User] [Fedora Linux Users] [Linux SCTP] [DCCP] [Gimp] [Yosemite News] [Deep Creek Hot Springs] [Yosemite Campsites] [ISDN Cause Codes]

Powered by Linux