[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190702153535.228365fea7f0063cceec96cd@linux-foundation.org>
Date: Tue, 2 Jul 2019 15:35:35 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Christoph Hellwig <hch@....de>, Jason Gunthorpe <jgg@...lanox.com>,
Jérôme Glisse <jglisse@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 16/25] device-dax: use the dev_pagemap internal refcount
On Fri, 28 Jun 2019 12:14:44 -0700 Dan Williams <dan.j.williams@...el.com> wrote:
> I believe -mm auto drops patches when they appear in the -next
> baseline. So it should "just work" to pull it into the series and send
> it along for -next inclusion.
Yup. Although it isn't very "auto" - I manually check that the patch
which turned up in -next was identical to the version which I had. If
not, I go find out why...
Powered by blists - more mailing lists