From: Bart Van Assche <bvanassche@acm.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH blktests v2 6/6] srp/rc: allow test with built-in sd_mod and sg drivers
Date: Thu, 18 Aug 2022 13:07:41 -0700 [thread overview]
Message-ID: <bbd13579-4279-8263-9d7d-684d7faa495f@acm.org> (raw)
In-Reply-To: <20220818012624.71544-7-shinichiro.kawasaki@wdc.com>
On 8/17/22 18:26, Shin'ichiro Kawasaki wrote:
> + required_drivers=(
> + sd_mod
> + sg
> + )
> + _have_drivers "${required_drivers[@]}"
Can the above be simplified into _have_drivers sd_mod sg?
Thanks,
Bart.
next prev parent reply other threads:[~2022-08-18 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 1:26 [PATCH blktests v2 0/6] fix module check issues Shin'ichiro Kawasaki
2022-08-18 1:26 ` [PATCH blktests v2 1/6] common/rc: avoid module load in _have_driver() Shin'ichiro Kawasaki
2022-08-18 20:02 ` Bart Van Assche
2022-08-19 0:34 ` Shinichiro Kawasaki
2022-08-19 1:03 ` Bart Van Assche
2022-08-19 1:33 ` Shinichiro Kawasaki
2022-08-18 1:26 ` [PATCH blktests v2 2/6] nbd/rc: load nbd module explicitly Shin'ichiro Kawasaki
2022-08-18 1:26 ` [PATCH blktests v2 3/6] common/rc: ensure modules are loadable in _have_modules() Shin'ichiro Kawasaki
2022-08-18 20:06 ` Bart Van Assche
2022-08-19 0:35 ` Shinichiro Kawasaki
2022-08-18 1:26 ` [PATCH blktests v2 4/6] common,tests: replace _have_driver() with _have_drivers() Shin'ichiro Kawasaki
2022-08-18 1:26 ` [PATCH blktests v2 5/6] block/001: use _have_drivers() in place of _have_modules() Shin'ichiro Kawasaki
2022-08-18 1:26 ` [PATCH blktests v2 6/6] srp/rc: allow test with built-in sd_mod and sg drivers Shin'ichiro Kawasaki
2022-08-18 20:07 ` Bart Van Assche [this message]
2022-08-19 0:36 ` 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=bbd13579-4279-8263-9d7d-684d7faa495f@acm.org \
--to=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox