From: Jonathan Corbet <corbet@lwn.net>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-doc@vger.kernel.org, linux-nvdimm@lists.01.org,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Andreas Dilger <adilger.kernel@dilger.ca>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.com>,
linux-fsdevel@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 1/2] dax: some small updates to dax.txt documentation
Date: Wed, 20 Jul 2016 17:13:02 -0600 [thread overview]
Message-ID: <20160720171302.13e14a0d@lwn.net> (raw)
In-Reply-To: <20160714214049.20075-1-ross.zwisler@linux.intel.com>
On Thu, 14 Jul 2016 15:40:48 -0600
Ross Zwisler <ross.zwisler@linux.intel.com> wrote:
> These are originally from Matthew Wilcox and were part of his huge
> "mm,fs,dax: Change ->pmd_fault to ->huge_fault" patch that was part of PUD
> support.
>
> I'm breaking these small changes out as they stand on their own and add
> useful information to Documentation/filesystems/dax.txt.
So how were you thinking of routing these? I can take the docs fix, of
course, but part 2 is a bit out of my turf. If you want to route them
together via another tree that's fine, just let me know.
Thanks,
jon
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-07-20 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 21:40 [PATCH 1/2] dax: some small updates to dax.txt documentation Ross Zwisler
2016-07-14 21:40 ` [PATCH 2/2] dax: remote unused fault wrappers Ross Zwisler
2016-07-18 12:03 ` Jan Kara
2016-07-20 23:13 ` Jonathan Corbet [this message]
2016-07-20 23:18 ` [PATCH 1/2] dax: some small updates to dax.txt documentation Andrew Morton
2016-07-20 23:24 ` Jonathan Corbet
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=20160720171302.13e14a0d@lwn.net \
--to=corbet@lwn.net \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
--cc=xfs@oss.sgi.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