From: Mike Snitzer <snitzer@redhat.com>
To: Lukas Herbolt <lherbolt@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Akira Hayakawa <ruby.wktk@gmail.com>
Subject: Re: dm-flakey NOT to return -EIO on READ?
Date: Fri, 29 Jul 2016 10:35:42 -0400 [thread overview]
Message-ID: <20160729143542.GA19246@redhat.com> (raw)
In-Reply-To: <CAM4Jq_4+RuRppTQXDBkp7Kg4tRV52pwcfEfm5HZtC88h0v-aWw@mail.gmail.com>
On Fri, Jul 29 2016 at 10:31am -0400,
Lukas Herbolt <lherbolt@redhat.com> wrote:
> - http://people.redhat.com/~lherbolt/dm-flakey/v4.7-dm_flakey.tar.gz
>
> Lukas
Please post an incremental patch relative to 4.7 or latest Linus
kernel. Don't make people suffer with tarballs of whatever you've
packaged above.
Mike
next prev parent reply other threads:[~2016-07-29 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 6:33 dm-flakey NOT to return -EIO on READ? Akira Hayakawa
2016-07-06 9:52 ` Lukas Herbolt
2016-07-06 12:54 ` Akira Hayakawa
2016-07-17 1:36 ` Akira Hayakawa
2016-07-29 6:25 ` Lukas Herbolt
2016-07-29 6:32 ` Akira Hayakawa
2016-07-29 14:31 ` Lukas Herbolt
2016-07-29 14:35 ` Mike Snitzer [this message]
2016-07-29 17:30 ` Mike Snitzer
2016-07-29 18:00 ` Lukas Herbolt
2016-07-29 22:55 ` Akira Hayakawa
2016-07-30 0:26 ` Akira Hayakawa
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=20160729143542.GA19246@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lherbolt@redhat.com \
--cc=ruby.wktk@gmail.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).