From: Eric Biggers <ebiggers@kernel.org>
To: linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: [PATCH 0/3] block: show crypto capabilities in sysfs
Date: Fri, 26 Nov 2021 13:25:11 -0800 [thread overview]
Message-ID: <20211126212514.173334-1-ebiggers@kernel.org> (raw)
This series adds sysfs files that expose the inline encryption
capabilities of request queues.
Patches 1 and 2 are some related cleanups for existing blk-sysfs code.
Patch 3 is the real change; see there for more details.
This applies to linux-block/for-next.
Eric Biggers (3):
block: simplify calling convention of elv_unregister_queue()
block: don't delete queue kobject before its children
blk-crypto: show crypto capabilities in sysfs
Documentation/block/queue-sysfs.rst | 30 +++++
block/Makefile | 3 +-
block/blk-crypto-internal.h | 12 ++
block/blk-crypto-sysfs.c | 177 ++++++++++++++++++++++++++++
block/blk-crypto.c | 3 +
block/blk-sysfs.c | 17 ++-
block/elevator.c | 8 +-
include/linux/blkdev.h | 1 +
8 files changed, 241 insertions(+), 10 deletions(-)
create mode 100644 block/blk-crypto-sysfs.c
base-commit: 4d162e24e9979dcb3d7825229982c172ca4bde54
--
2.34.1
next reply other threads:[~2021-11-26 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 21:25 Eric Biggers [this message]
2021-11-26 21:25 ` [PATCH 1/3] block: simplify calling convention of elv_unregister_queue() Eric Biggers
2021-11-26 21:25 ` [PATCH 2/3] block: don't delete queue kobject before its children Eric Biggers
2021-11-26 21:25 ` [PATCH 3/3] blk-crypto: show crypto capabilities in sysfs Eric Biggers
2021-11-27 9:06 ` Greg KH
2021-11-27 20:47 ` Eric Biggers
2021-11-28 8:14 ` Greg KH
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=20211126212514.173334-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@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 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.