public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
	linux-doc@vger.kernel.org, linux-nvdimm@ml01.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>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	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:24:17 -0600	[thread overview]
Message-ID: <20160720172417.7f0c49d3@lwn.net> (raw)
In-Reply-To: <20160720161857.a60913d6fae98c4c594e2e51@linux-foundation.org>

On Wed, 20 Jul 2016 16:18:57 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> > 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.  
> 
> I have them queued.  You were cc'ed on the commit!

Interesting, I can't find that cc in my archive anywhere.  It seems it
went astray somewhere?

Thanks,

jon

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2016-07-20 23:24 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 ` [PATCH 1/2] dax: some small updates to dax.txt documentation Jonathan Corbet
2016-07-20 23:18   ` Andrew Morton
2016-07-20 23:24     ` Jonathan Corbet [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=20160720172417.7f0c49d3@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@ml01.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