Linux block layer
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Josef Bacik <josef@toxicpanda.com>
Subject: [PATCH v2 0/4] null_blk cleanup and device naming improvements
Date: Wed, 20 Apr 2022 09:57:14 +0900	[thread overview]
Message-ID: <20220420005718.3780004-1-damien.lemoal@opensource.wdc.com> (raw)

The first 3 patches of this series are simple code cleanups.

The last patch changes the device naming scheme for devices created
through configfs: the configfs device directory name is used as the disk
name. This name is also checked against potentially exiting nullb
devices created during modprobe when the nr_device module option is not
0.

This series falls short of pre-populating configfs with directories
corresponding to the devices created during modprobe as this is not
easily feasible. However, the added device name check avoids mistakes by
users about reusing configfs names already used by existing devices.

Changes from v1:
* Modified patch 3 to use the pr_fmt() macro instead of manually adding
  null_blk prefix to messages.
* Fixed patch 4 commit message

Damien Le Moal (4):
  block: null_blk: Fix code style issues
  block: null_blk: Cleanup device creation and deletion
  block: null_blk: Cleanup messages
  block: null_blk: Improve device creation with configfs

 drivers/block/null_blk/main.c  | 91 +++++++++++++++++++++++++---------
 drivers/block/null_blk/zoned.c |  7 ++-
 2 files changed, 73 insertions(+), 25 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-04-20  0:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  0:57 Damien Le Moal [this message]
2022-04-20  0:57 ` [PATCH v2 1/4] block: null_blk: Fix code style issues Damien Le Moal
2022-04-20  3:51   ` Chaitanya Kulkarni
2022-04-20  7:56   ` Johannes Thumshirn
2022-04-20  0:57 ` [PATCH v2 2/4] block: null_blk: Cleanup device creation and deletion Damien Le Moal
2022-04-20  3:53   ` Chaitanya Kulkarni
2022-04-20  7:57   ` Johannes Thumshirn
2022-04-20  0:57 ` [PATCH v2 3/4] block: null_blk: Cleanup messages Damien Le Moal
2022-04-20  3:57   ` Chaitanya Kulkarni
2022-04-20  5:05     ` Damien Le Moal
2022-04-20  0:57 ` [PATCH v2 4/4] block: null_blk: Improve device creation with configfs Damien Le Moal
2022-04-20  7:58   ` Johannes Thumshirn
2022-05-03 20:03 ` [PATCH v2 0/4] null_blk cleanup and device naming improvements Jens Axboe

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=20220420005718.3780004-1-damien.lemoal@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=axboe@kernel.dk \
    --cc=josef@toxicpanda.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox