From: Eric Biggers <ebiggers@kernel.org>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Satya Tangirala <satyaprateek2357@gmail.com>,
dm-devel@redhat.com, linux-mmc@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [dm-devel] [PATCH v3 0/4] blk-crypto cleanups
Date: Mon, 27 Sep 2021 11:09:05 -0700 [thread overview]
Message-ID: <YVIIwUv9Vwd2dFt8@gmail.com> (raw)
In-Reply-To: <20210923185629.54823-1-ebiggers@kernel.org>
On Thu, Sep 23, 2021 at 11:56:25AM -0700, Eric Biggers wrote:
> This series renames struct blk_keyslot_manager to struct
> blk_crypto_profile, as it is misnamed; it doesn't always manage
> keyslots. It's much more logical to think of it as the
> "blk-crypto profile" of a device, similar to blk_integrity_profile.
>
> This series also improves the inline-encryption.rst documentation file,
> and cleans up blk-crypto-fallback a bit.
>
> This series applies to v5.15-rc2.
>
> Changed v2 => v3:
> - Made some minor tweaks to patches 3 and 4, mostly comments and
> documentation.
> - Clarified a commit message to mention no change in behavior.
> - Added a Reviewed-by tag.
>
> Changed v1 => v2:
> - Fixed a build error in blk-integrity.c.
> - Removed a mention of "ksm" from a comment.
> - Dropped the patch "blk-crypto-fallback: consolidate static variables".
> - Added Acked-by and Reviewed-by tags.
>
> Eric Biggers (4):
> blk-crypto-fallback: properly prefix function and struct names
> blk-crypto: rename keyslot-manager files to blk-crypto-profile
> blk-crypto: rename blk_keyslot_manager to blk_crypto_profile
> blk-crypto: update inline encryption documentation
Any more feedback on this? If there are any objections to the renaming of
blk_keyslot_manager to blk_crypto_profile, now is the time to speak up.
- 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: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Satya Tangirala <satyaprateek2357@gmail.com>,
dm-devel@redhat.com, linux-mmc@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v3 0/4] blk-crypto cleanups
Date: Mon, 27 Sep 2021 11:09:05 -0700 [thread overview]
Message-ID: <YVIIwUv9Vwd2dFt8@gmail.com> (raw)
In-Reply-To: <20210923185629.54823-1-ebiggers@kernel.org>
On Thu, Sep 23, 2021 at 11:56:25AM -0700, Eric Biggers wrote:
> This series renames struct blk_keyslot_manager to struct
> blk_crypto_profile, as it is misnamed; it doesn't always manage
> keyslots. It's much more logical to think of it as the
> "blk-crypto profile" of a device, similar to blk_integrity_profile.
>
> This series also improves the inline-encryption.rst documentation file,
> and cleans up blk-crypto-fallback a bit.
>
> This series applies to v5.15-rc2.
>
> Changed v2 => v3:
> - Made some minor tweaks to patches 3 and 4, mostly comments and
> documentation.
> - Clarified a commit message to mention no change in behavior.
> - Added a Reviewed-by tag.
>
> Changed v1 => v2:
> - Fixed a build error in blk-integrity.c.
> - Removed a mention of "ksm" from a comment.
> - Dropped the patch "blk-crypto-fallback: consolidate static variables".
> - Added Acked-by and Reviewed-by tags.
>
> Eric Biggers (4):
> blk-crypto-fallback: properly prefix function and struct names
> blk-crypto: rename keyslot-manager files to blk-crypto-profile
> blk-crypto: rename blk_keyslot_manager to blk_crypto_profile
> blk-crypto: update inline encryption documentation
Any more feedback on this? If there are any objections to the renaming of
blk_keyslot_manager to blk_crypto_profile, now is the time to speak up.
- Eric
next prev parent reply other threads:[~2021-09-27 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 18:56 [dm-devel] [PATCH v3 0/4] blk-crypto cleanups Eric Biggers
2021-09-23 18:56 ` Eric Biggers
2021-09-23 18:56 ` [dm-devel] [PATCH v3 1/4] blk-crypto-fallback: properly prefix function and struct names Eric Biggers
2021-09-23 18:56 ` Eric Biggers
2021-09-23 18:56 ` [dm-devel] [PATCH v3 2/4] blk-crypto: rename keyslot-manager files to blk-crypto-profile Eric Biggers
2021-09-23 18:56 ` Eric Biggers
2021-09-23 18:56 ` [dm-devel] [PATCH v3 3/4] blk-crypto: rename blk_keyslot_manager to blk_crypto_profile Eric Biggers
2021-09-23 18:56 ` Eric Biggers
2021-09-23 18:56 ` [dm-devel] [PATCH v3 4/4] blk-crypto: update inline encryption documentation Eric Biggers
2021-09-23 18:56 ` Eric Biggers
2021-09-27 18:09 ` Eric Biggers [this message]
2021-09-27 18:09 ` [PATCH v3 0/4] blk-crypto cleanups Eric Biggers
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=YVIIwUv9Vwd2dFt8@gmail.com \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satyaprateek2357@gmail.com \
/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.