From: Andrew Morton <akpm@linux-foundation.org>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Dan Williams <dan.j.williams@intel.com>
Subject: Re: [GIT PULL] dax-fixes for 4.5-rc6
Date: Fri, 26 Feb 2016 14:33:30 -0800 [thread overview]
Message-ID: <20160226143330.c69e1970f1a254564d2886b1@linux-foundation.org> (raw)
In-Reply-To: <20160226214336.GA5886@linux.intel.com>
On Fri, 26 Feb 2016 14:43:36 -0700 Ross Zwisler <ross.zwisler@linux.intel.com> wrote:
> On Wed, Feb 24, 2016 at 02:19:31PM -0800, Andrew Morton wrote:
> > On Wed, 24 Feb 2016 14:03:22 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > > On Wed, Feb 24, 2016 at 10:42 AM, Ross Zwisler
> > > <ross.zwisler@linux.intel.com> wrote:
> > > >
> > > > I know DAX fixes have historically gone up through Andrew Morton's -mm tree,
> > > > but for some reason he's been silent on this series for the last few weeks. I
> > > > think that the problems being fixed are important enough that we really
> > > > shouldn't wait until v4.6.
> > >
> > > Andrew, can you comment?
> > >
> >
> > It's been a bit confusing because Dan has been merging DAX stuff as
> > well, mainly on the fs side. I had assumed that these patches were
> > aimed at that route also.
> >
> > I'll take a look right now.
>
> Any update on this for v4.5, or is this now v4.6 material?
Patience, grasshopper. It's only been in -next for one day.
prev parent reply other threads:[~2016-02-26 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 18:42 [GIT PULL] dax-fixes for 4.5-rc6 Ross Zwisler
2016-02-24 22:03 ` Linus Torvalds
2016-02-24 22:19 ` Andrew Morton
2016-02-24 22:57 ` Dan Williams
2016-02-26 21:43 ` Ross Zwisler
2016-02-26 22:33 ` Andrew Morton [this message]
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=20160226143330.c69e1970f1a254564d2886b1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/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).