From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751199AbdFDXuA (ORCPT <rfc822;w@1wt.eu>);
        Sun, 4 Jun 2017 19:50:00 -0400
Received: from ozlabs.org ([103.22.144.67]:48297 "EHLO ozlabs.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751147AbdFDXt6 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 4 Jun 2017 19:49:58 -0400
Date: Mon, 5 Jun 2017 09:49:56 +1000
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
        linux-kernel@vger.kernel.org
Subject: Re: new tree for linux-next: uuid
Message-ID: <20170605094956.069d5af3@canb.auug.org.au>
In-Reply-To: <20170604201413.GA12748@lst.de>
References: <20170604201413.GA12748@lst.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Christoph,

On Sun, 4 Jun 2017 22:14:13 +0200 Christoph Hellwig <hch@lst.de> wrote:
>
> can you please include my uuid tree at:
> 
> 	git://git.infradead.org/users/hch/uuid.git for-next
> 
> into linux-next?  We've been doing a fair amount of work on the
> uuid library and I plan to send it and some work that will pile
> up on top of it to Linus for the next merge window.

Added from today.

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