From: Omar Sandoval <osandov@osandov.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, Omar Sandoval <osandov@fb.com>,
Masato Suzuki <masato.suzuki@wdc.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH blktests 0/3] Fix partition device sysfs access
Date: Mon, 11 Mar 2019 13:20:47 -0700 [thread overview]
Message-ID: <20190311202047.GA30813@vader> (raw)
In-Reply-To: <20190305052447.24291-1-shinichiro.kawasaki@wdc.com>
On Tue, Mar 05, 2019 at 02:24:44PM +0900, Shin'ichiro Kawasaki wrote:
> This patch series fixes test failures found in the zbd test group when run on
> partition devices. The failure cause is a block device sysfs attributes access
> problem if the target device is a partition.
>
> This series resends patches 3, 4 and 5 posted as a part of another series.
>
> https://www.spinics.net/lists/linux-block/msg37431.html
>
> The patches reflect the review comments by Omar made on the list.
>
> Shin'ichiro Kawasaki (3):
> check: Add TEST_DEV_PART_SYSFS variable
> common: Add _test_dev_is_partition() helper function
> zbd: Change sysfs path for partition devices
>
> check | 46 +++++++++++++++++++++++++---------------------
> common/rc | 8 ++++++++
> new | 16 ++++++++++++++--
> tests/zbd/rc | 8 ++++++--
> 4 files changed, 53 insertions(+), 25 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2019-03-11 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 5:24 [PATCH blktests 0/3] Fix partition device sysfs access Shin'ichiro Kawasaki
2019-03-05 5:24 ` [PATCH blktests 1/3] check: Add TEST_DEV_PART_SYSFS variable Shin'ichiro Kawasaki
2019-03-05 5:24 ` [PATCH blktests 2/3] common: Add _test_dev_is_partition() helper function Shin'ichiro Kawasaki
2019-03-05 5:24 ` [PATCH blktests 3/3] zbd: Change sysfs path for partition devices Shin'ichiro Kawasaki
2019-03-11 20:20 ` Omar Sandoval [this message]
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=20190311202047.GA30813@vader \
--to=osandov@osandov.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=masato.suzuki@wdc.com \
--cc=osandov@fb.com \
--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.