All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org
Subject: reduce the dependency on modules v2
Date: Wed,  1 Jun 2022 08:48:30 +0200	[thread overview]
Message-ID: <20220601064837.3473709-1-hch@lst.de> (raw)

Hi Shin'ichiro,

this series reduces the dependency of blktests on modular builds
of various block drivers.  There are still plenty of tests that
do require modules, mostly because a lot of scsi_debug and null_blk
can only be set at load time, but I plan to address those in the
kernel soon.

Changes since v1:
 - drop the partial null_blk and scsi_debug changes.  They caused to
   much trouble for just enabling one test each.
 - more quoting
 - two spelling fixes

             reply	other threads:[~2022-06-01  6:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  6:48 Christoph Hellwig [this message]
2022-06-01  6:48 ` [PATCH blktests 1/7] nvme: use _have_loop instead of _have_modules loop Christoph Hellwig
2022-06-01  6:48 ` [PATCH blktests 2/7] common: add a helper if a driver is available Christoph Hellwig
2022-06-01  6:48 ` [PATCH blktests 3/7] common: fix _have_module_param_value to work with built-in drivers Christoph Hellwig
2022-06-01  6:48 ` [PATCH blktests 4/7] common: do not require loop support to be modular Christoph Hellwig
2022-06-01  6:48 ` [PATCH blktests 5/7] nbd: do not require nbd " Christoph Hellwig
2022-06-01  6:48 ` [PATCH blktests 6/7] scsi: don't require sg to be built in Christoph Hellwig
2022-06-01  6:48 ` [PATCH blktests 7/7] nvme: don't require the nvme drivers " Christoph Hellwig
2022-06-03  1:23 ` reduce the dependency on modules v2 Shinichiro Kawasaki

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=20220601064837.3473709-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.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.