From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>, dm-devel@redhat.com
Subject: Re: [PATCH 0/4] dm-writecache patches
Date: Wed, 30 May 2018 09:23:11 -0400 [thread overview]
Message-ID: <20180530132311.GA5157@redhat.com> (raw)
In-Reply-To: <20180530131654.271798747@debian.vm>
On Wed, May 30 2018 at 9:16am -0400,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> Here I'm sending the current dm-writecache patch.
> The per-architecture switch was removed.
>
> Some reported bugs are fixed.
I've staged dm-writecache in linux-dm.git's dm-4.18 branch. Please
rebase ontop of that.
In particular, as I said in an earlier email, I'd really appreciate an
incremental patch that removes the per-architecture flushing.
Thanks,
Mike
next prev parent reply other threads:[~2018-05-30 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 13:16 [PATCH 0/4] dm-writecache patches Mikulas Patocka
2018-05-30 13:23 ` Mike Snitzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-19 5:25 [patch " Mikulas Patocka
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=20180530132311.GA5157@redhat.com \
--to=snitzer@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@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