From: Mike Snitzer <snitzer@redhat.com>
To: heinzm@redhat.com
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 1/2] dm-raid: add RAID discard support
Date: Thu, 25 Sep 2014 14:02:58 -0400 [thread overview]
Message-ID: <20140925180258.GA30170@redhat.com> (raw)
In-Reply-To: <1411573639-21610-1-git-send-email-heinzm@redhat.com>
On Wed, Sep 24 2014 at 11:47am -0400,
heinzm@redhat.com <heinzm@redhat.com> wrote:
> From: Heinz Mauelshagen <heinzm@redhat.com>
>
> (Folding patches 2+3 of my previous series into one on Mike Snitzers request)
I've tweaked and then folded these 2 new patches too. I see no need to
"show your work" for such a simple change; especially given the rather
fundamental raid_check_discard() implementation differences that patch 2
introduced.
Anyway, end result is staged in linux-next for v3.18 inclusion, see:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=d679f9a5582b21eff85f759f5e6a9e2ffb4793e5
next prev parent reply other threads:[~2014-09-25 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 15:47 [PATCH 1/2] dm-raid: add RAID discard support heinzm
2014-09-25 18:02 ` Mike Snitzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-24 14:12 heinzm
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=20140925180258.GA30170@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@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