From: David Sterba <dsterba@suse.cz>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: david@fromorbit.com, guaneryu@gmail.com, fstests@vger.kernel.org
Subject: Re: [PATCH v2] common: Add _dmsetup_create and _dmsetup_remove helpers
Date: Wed, 27 Jun 2018 14:10:54 +0200 [thread overview]
Message-ID: <20180627121054.GB2287@suse.cz> (raw)
In-Reply-To: <1530096852-4165-1-git-send-email-yangx.jy@cn.fujitsu.com>
On Wed, Jun 27, 2018 at 06:54:12PM +0800, Xiao Yang wrote:
> Make sure both "$UDEV_SETTLE_PROG" and "mknodes" can always
> be run after a dm create or remove operation.
>
> Suggested-by: Dave Chinner <david@fromorbit.com>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
The helpers are better, thanks.
Reviewed-by: David Sterba <dsterba@suse.com>
next prev parent reply other threads:[~2018-06-27 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 10:59 [PATCH] generic/085: Call $UDEV_SETTLE_PROG before "dmsetup remove" Xiao Yang
2018-06-27 7:54 ` Dave Chinner
2018-06-27 10:54 ` [PATCH v2] common: Add _dmsetup_create and _dmsetup_remove helpers Xiao Yang
2018-06-27 12:10 ` David Sterba [this message]
2018-06-28 1:45 ` [PATCH v3] " Xiao Yang
2018-06-28 1:42 ` [PATCH v2] " Xiao Yang
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=20180627121054.GB2287@suse.cz \
--to=dsterba@suse.cz \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=yangx.jy@cn.fujitsu.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