All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: XArray -next inclusion request
Date: Sun, 17 Jun 2018 13:41:04 +1000	[thread overview]
Message-ID: <20180617134104.68c24ffc@canb.auug.org.au> (raw)
In-Reply-To: <20180617021521.GA18455@bombadil.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

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.

> 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.

No worries, I will check your other branch and if things are still to
difficult, you will get an email and I will just drop it for a few days.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-06-17  3:41 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 [this message]
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=20180617134104.68c24ffc@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.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 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.