From: Ross Zwisler <ross.zwisler@linux.intel.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>,
"david@fromorbit.com" <david@fromorbit.com>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: what's in nvdimm.git for v4.4?
Date: Wed, 21 Oct 2015 15:58:18 -0600 [thread overview]
Message-ID: <20151021215818.GA640@linux.intel.com> (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:
> ===
<snip>
> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Ross Zwisler <ross.zwisler@linux.intel.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@ml01.01.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"david@fromorbit.com" <david@fromorbit.com>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: what's in nvdimm.git for v4.4?
Date: Wed, 21 Oct 2015 15:58:18 -0600 [thread overview]
Message-ID: <20151021215818.GA640@linux.intel.com> (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:
> ===
<snip>
> 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.
next prev parent reply other threads:[~2015-10-21 21:58 UTC|newest]
Thread overview: 24+ 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-20 23:31 ` Williams, Dan J
2015-10-21 0:01 ` Dave Chinner
2015-10-21 0:01 ` Dave Chinner
2015-10-21 0:31 ` Dan Williams
2015-10-21 0:31 ` Dan Williams
2015-10-21 2:38 ` Dave Chinner
2015-10-21 2:38 ` Dave Chinner
2015-10-21 3:17 ` Dan Williams
2015-10-21 3:17 ` Dan Williams
2015-10-21 9:08 ` Jan Kara
2015-10-21 9:08 ` Jan Kara
2015-10-21 16:54 ` Dan Williams
2015-10-21 16:54 ` Dan Williams
2015-10-21 22:36 ` Elliott, Robert (Persistent Memory)
2015-10-21 22:36 ` Elliott, Robert (Persistent Memory)
2015-10-21 22:50 ` Dan Williams
2015-10-21 22:50 ` Dan Williams
2015-10-21 17:47 ` Jens Axboe
2015-10-21 17:47 ` Jens Axboe
2015-10-21 22:18 ` Dan Williams
2015-10-21 22:18 ` Dan Williams
2015-10-21 21:58 ` Ross Zwisler [this message]
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=20151021215818.GA640@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.