From: Dave Chinner <david@fromorbit.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "axboe@fb.com" <axboe@fb.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: what's in nvdimm.git for v4.4?
Date: Wed, 21 Oct 2015 11:01:03 +1100 [thread overview]
Message-ID: <20151021000103.GA19199@dastard> (raw)
In-Reply-To: <1445383903.6611.39.camel@intel.com>
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:
> ===
...
> Dave Chinner (5):
> xfs: fix inode size update overflow in xfs_map_direct()
> xfs: introduce BMAPI_ZERO for allocating zeroed extents
> xfs: Don't use unwritten extents for DAX
> xfs: DAX does not use IO completion callbacks
> xfs: add ->pfn_mkwrite support for DAX
Please drop these. They have not been reviewed yet, and because
the changes affect more than just DAX (core XFS allocator
functionality was changed) these need to go through the XFS tree.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-10-21 0:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 23:31 what's in nvdimm.git for v4.4? Williams, Dan J
2015-10-21 0:01 ` Dave Chinner [this message]
2015-10-21 0:31 ` Dan Williams
2015-10-21 2:38 ` Dave Chinner
2015-10-21 3:17 ` Dan Williams
2015-10-21 9:08 ` Jan Kara
2015-10-21 16:54 ` Dan Williams
2015-10-21 22:36 ` Elliott, Robert (Persistent Memory)
2015-10-21 22:50 ` Dan Williams
2015-10-21 17:47 ` Jens Axboe
2015-10-21 22:18 ` Dan Williams
2015-10-21 21:58 ` Ross Zwisler
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=20151021000103.GA19199@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=martin.petersen@oracle.com \
--cc=rafael.j.wysocki@intel.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).