From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: XArray -next inclusion request
Date: Sat, 16 Jun 2018 19:15:22 -0700 [thread overview]
Message-ID: <20180617021521.GA18455@bombadil.infradead.org> (raw)
Hi Stephen,
Please add
git://git.infradead.org/users/willy/linux-dax.git xarray
to linux-next. It is based on -rc1. You will find some conflicts
against Dan's current patches to DAX; these are all resolved correctly
in the xarray-20180615 branch which is based on next-20180615.
In a masterstroke of timing, I'm going to be on a plane to Tokyo on
Monday. If this causes any problems, please just ignore the request
for now and we'll resolve it when I'm available to fix problems.
next reply other threads:[~2018-06-17 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 2:15 Matthew Wilcox [this message]
2018-06-17 3:41 ` XArray -next inclusion request Stephen Rothwell
2018-07-04 22:54 ` Matthew Wilcox
2018-07-05 4:37 ` Stephen Rothwell
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=20180617021521.GA18455@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sfr@canb.auug.org.au \
/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).