From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Subject: cleanup block layer sysfs handling
Date: Fri, 24 Jun 2022 07:25:04 +0200 [thread overview]
Message-ID: <20220624052510.3996673-1-hch@lst.de> (raw)
Hi Jens,
this series cleans up various loose ends in the block layer sysfs handling.
It sits on top of the "fully tear down the queue in del_gendisk" series
submitted last week.
Diffstat:
block/blk-mq-sysfs.c | 45 +++++++++++++++++++++----------------------
block/blk-mq.c | 4 +--
block/blk-mq.h | 7 +++---
block/blk-sysfs.c | 36 ++++++++++------------------------
block/blk.h | 2 +
block/genhd.c | 3 ++
block/partitions/core.c | 1
include/linux/blk-mq.h | 1
include/linux/blktrace_api.h | 10 ---------
kernel/trace/blktrace.c | 11 ----------
10 files changed, 44 insertions(+), 76 deletions(-)
next reply other threads:[~2022-06-24 5:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 5:25 Christoph Hellwig [this message]
2022-06-24 5:25 ` [PATCH 1/6] block: simplify blktrace sysfs attribute creation Christoph Hellwig
2022-06-25 2:57 ` Bart Van Assche
2022-06-24 5:25 ` [PATCH 2/6] block: remove a superflous queue kobject reference Christoph Hellwig
2022-06-25 2:59 ` Bart Van Assche
2022-06-24 5:25 ` [PATCH 3/6] block: use default groups to register the queue attributes Christoph Hellwig
2022-06-25 3:00 ` Bart Van Assche
2022-06-24 5:25 ` [PATCH 4/6] block: remove the extra gendisk reference in __blk_mq_register_dev Christoph Hellwig
2022-06-25 3:01 ` Bart Van Assche
2022-06-24 5:25 ` [PATCH 5/6] blk-mq: rename blk_mq_sysfs_{,un}register Christoph Hellwig
2022-06-25 3:07 ` Bart Van Assche
2022-06-24 5:25 ` [PATCH 6/6] blk-mq: cleanup disk sysfs registration Christoph Hellwig
2022-06-25 3:09 ` Bart Van Assche
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=20220624052510.3996673-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--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 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.