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: Re: XArray -next inclusion request
Date: Wed, 4 Jul 2018 15:54:31 -0700 [thread overview]
Message-ID: <20180704225431.GA16309@bombadil.infradead.org> (raw)
In-Reply-To: <20180617134104.68c24ffc@canb.auug.org.au>
On Sun, Jun 17, 2018 at 01:41:04PM +1000, Stephen Rothwell wrote:
> Hi Willy,
>
> On Sat, 16 Jun 2018 19:15:22 -0700 Matthew Wilcox <willy@infradead.org> wrote:
> >
> > 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.
>
> Added from tomorrow.
Thanks! I have some additional patches for the IDA that I'd like to
send to Linus as a separate pull request. Unfortunately, they conflict with
the XArray patches, so I've done them as a separate branch in the same tree:
git://git.infradead.org/users/willy/linux-dax.git ida
Would you prefer to add them as a separate branch to linux-next (to be
pulled after xarray), or would you prefer to replace the xarray pull
with the ida pull? Either way, you'll get the same commits as the ida
branch is based off the xarray branch.
next prev parent reply other threads:[~2018-07-04 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 2:15 XArray -next inclusion request Matthew Wilcox
2018-06-17 3:41 ` Stephen Rothwell
2018-07-04 22:54 ` Matthew Wilcox [this message]
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=20180704225431.GA16309@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 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.