From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ross Zwisler Subject: Re: what's in nvdimm.git for v4.4? Date: Wed, 21 Oct 2015 15:58:18 -0600 Message-ID: <20151021215818.GA640@linux.intel.com> References: <1445383903.6611.39.camel@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "axboe@fb.com" , "akpm@linux-foundation.org" , "Wysocki, Rafael J" , "linux-kernel@vger.kernel.org" , "hch@lst.de" , "martin.petersen@oracle.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "david@fromorbit.com" , "jack@suse.cz" To: "Williams, Dan J" Return-path: Content-Disposition: inline In-Reply-To: <1445383903.6611.39.camel@intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Oct 20, 2015 at 11:31:45PM +0000, Williams, Dan J wrote: > Here is a status summary of the topic-branches nvdimm.git is tracking > for v4.4. Unless indicated these branches are not present in -next. > Please ACK, NAK, or ask for a re-post of any of the below to disposition > it for the merge window. > > === > for-4.4/dax-fixes: > === > Ross Zwisler (2): > dax: dax_pfn_mkwrite() truncate race check We can drop this patch for dax_pfn_mkwrite() as that whole function is going away after we merge the locking fixes from XFS, ext2 and ext4.