From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Mike Snitzer <msnitzer@redhat.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
Christoph Hellwig <hch@infradead.org>,
device-mapper development <dm-devel@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [dm-devel] [PATCH] dm-writecache
Date: Mon, 12 Mar 2018 00:48:59 -0700 [thread overview]
Message-ID: <20180312074859.GB30695@infradead.org> (raw)
In-Reply-To: <CAPcyv4gBUt5NYK2Lx0dMZAnENeSgKm3KaUvY9kkqB+PNPyQu4w@mail.gmail.com>
On Thu, Mar 08, 2018 at 09:08:32AM -0800, Dan Williams wrote:
> I had the same feedback, and Mikulas sent this useful enhancement to
> the memcpy_flushcache API:
>
> https://patchwork.kernel.org/patch/10217655/
>
> ...it's in my queue to either push through -tip or add it to the next
> libnvdimm pull request for 4.17-rc1.
So lets rebase this submission on top of that.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-03-12 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.02.1803080824210.2819@file01.intranet.prod.int.rdu2.redhat.com>
2018-03-08 14:51 ` [dm-devel] [PATCH] dm-writecache Christoph Hellwig
2018-03-08 17:08 ` Dan Williams
2018-03-12 7:48 ` Christoph Hellwig [this message]
2018-03-12 12:15 ` Mikulas Patocka
2018-05-18 15:44 ` dm-writecache Mike Snitzer
2018-05-18 15:54 ` dm-writecache Dan Williams
2018-05-18 20:12 ` dm-writecache Mikulas Patocka
2018-05-18 20:14 ` dm-writecache Dan Williams
2018-05-18 22:00 ` dm-writecache Mikulas Patocka
2018-05-18 22:10 ` dm-writecache Dan Williams
2018-03-09 3:26 ` [dm-devel] [PATCH] dm-writecache Mikulas Patocka
2018-03-12 7:50 ` Christoph Hellwig
2018-03-12 12:12 ` 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=20180312074859.GB30695@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=linux-nvdimm@lists.01.org \
--cc=mpatocka@redhat.com \
--cc=msnitzer@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).