linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [patch 4/4] dm-writecache: use new API for flushing
Date: Wed, 30 May 2018 09:26:47 -0400	[thread overview]
Message-ID: <20180530132647.GB5157@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1805300919070.11327@file01.intranet.prod.int.rdu2.redhat.com>

On Wed, May 30 2018 at  9:21am -0400,
Mikulas Patocka <mpatocka@redhat.com> wrote:

> 
> 
> On Wed, 30 May 2018, Mike Snitzer wrote:
> 
> > That is really great news, can you submit an incremental patch that
> > layers ontop of the linux-dm.git 'dm-4.18' branch?
> > 
> > Thanks,
> > Mike
> 
> I've sent the current version that I have. I fixed the bugs that were 
> reported here (missing DAX, dm_bufio_client_create, __branch_check__ 
> long->int truncation).

OK, but a monolithic dm-writecache.c is no longer useful to me.  I can
drop Arnd's gcc warning fix (with the idea that Ingo or Steve will take
your __branch_check__ patch).  Not sure what the dm_bufio_client_create
fix is... must've missed a report about that.

ANyway, point is we're on too a different phase of dm-writecache.c's
development.  I've picked it up and am trying to get it ready for the
4.18 merge window (likely opening Sunday).  Therefore it needs to be in
a git tree, and incremental changes overlayed.  I cannot be rebasing at
this late stage in the 4.18 development window.

Thanks,
Mike

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2018-05-30 13:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180519052503.325953342@debian.vm>
     [not found] ` <20180519052635.567438191@debian.vm>
2018-05-22  6:39   ` [dm-devel] [patch 4/4] dm-writecache: use new API for flushing Christoph Hellwig
2018-05-22 18:41     ` Mike Snitzer
2018-05-22 19:00       ` Dan Williams
2018-05-22 19:19         ` Mike Snitzer
2018-05-22 19:27           ` Dan Williams
2018-05-22 20:52             ` Mike Snitzer
2018-05-22 22:53               ` [dm-devel] " Jeff Moyer
2018-05-23 20:57                 ` Mikulas Patocka
2018-05-28 13:52             ` Mikulas Patocka
2018-05-28 17:41               ` Dan Williams
2018-05-30 13:42                 ` [dm-devel] " Jeff Moyer
2018-05-30 13:51                   ` Mikulas Patocka
2018-05-30 13:52                   ` Jeff Moyer
2018-05-24  8:15         ` Mikulas Patocka
     [not found]   ` <CAPcyv4iEtfuVGPR0QMKcafv2XFwSj3nzxjX8cuXpXe00akAvYA@mail.gmail.com>
     [not found]     ` <alpine.LRH.2.02.1805250213270.13894@file01.intranet.prod.int.rdu2.redhat.com>
2018-05-25 12:51       ` Mike Snitzer
2018-05-25 15:57         ` Dan Williams
2018-05-26  7:02           ` Mikulas Patocka
2018-05-26 15:26             ` Dan Williams
2018-05-28 13:32               ` Mikulas Patocka
2018-05-28 18:14                 ` Dan Williams
2018-05-30 13:07                   ` Mikulas Patocka
2018-05-30 13:16                     ` Mike Snitzer
2018-05-30 13:21                       ` Mikulas Patocka
2018-05-30 13:26                         ` Mike Snitzer [this message]
2018-05-30 13:33                           ` Mikulas Patocka
2018-05-30 13:54                             ` Mike Snitzer
2018-05-30 14:09                               ` Mikulas Patocka
2018-05-30 14:21                                 ` Mike Snitzer
2018-05-30 14:46                                   ` Mikulas Patocka
2018-05-31  3:42                                     ` Mike Snitzer
2018-06-03 15:03                                       ` Mikulas Patocka
2018-05-31  3:39                                 ` Mike Snitzer
2018-05-31  8:16                                   ` Mikulas Patocka
2018-05-31 12:09                                     ` Mike Snitzer
2018-05-30 15:58                     ` Dan Williams
2018-05-30 22:39                       ` Dan Williams
2018-05-31  8:19                         ` Mikulas Patocka
2018-05-31 14:51                           ` Dan Williams
2018-05-31 15:31                             ` Mikulas Patocka
2018-05-31 16:39                               ` Dan Williams

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=20180530132647.GB5157@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-nvdimm@lists.01.org \
    --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;
as well as URLs for NNTP newsgroup(s).