From: Jonathan Corbet <corbet@lwn.net>
To: Nikolay Borisov <nborisov@suse.com>
Cc: snitzer@redhat.com, linux-doc@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH] dm flakey: Document "error_writes" feature
Date: Fri, 12 Oct 2018 11:31:54 -0600 [thread overview]
Message-ID: <20181012113154.7d2f4a64@lwn.net> (raw)
In-Reply-To: <1539073891-7701-1-git-send-email-nborisov@suse.com>
On Tue, 9 Oct 2018 11:31:31 +0300
Nikolay Borisov <nborisov@suse.com> wrote:
> Commit ef548c551e72 ("dm flakey: introduce "error_writes" feature")
> added the ability to dm flakey to error out writes in contrast to
> silently dropping it with 'drop_writes'. Unfortunately this feature
> is not currently documented and one has to be either familiar with the
> source code of dm flakey or check out xfstests sources to know of
> this parameter. So document it.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Applied to the docs tree, thanks.
jon
prev parent reply other threads:[~2018-10-12 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 8:31 [PATCH] dm flakey: Document "error_writes" feature Nikolay Borisov
2018-10-10 12:18 ` [dm-devel] " John Pittman
2018-10-12 17:31 ` Jonathan Corbet [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=20181012113154.7d2f4a64@lwn.net \
--to=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).