From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756940AbdKOEiU (ORCPT ); Tue, 14 Nov 2017 23:38:20 -0500 Received: from ozlabs.org ([103.22.144.67]:53701 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752853AbdKOEiN (ORCPT ); Tue, 14 Nov 2017 23:38:13 -0500 Date: Wed, 15 Nov 2017 15:38:11 +1100 From: Stephen Rothwell To: Mathieu Desnoyers Cc: "Paul E. McKenney" , linux-kernel Subject: Re: Adding rseq tree to -next Message-ID: <20171115153811.429a6af2@canb.auug.org.au> In-Reply-To: <1651801506.15291.1510708924508.JavaMail.zimbra@efficios.com> References: <210317081.15258.1510703646315.JavaMail.zimbra@efficios.com> <20171115111539.68aa2539@canb.auug.org.au> <1651801506.15291.1510708924508.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mathieu, On Wed, 15 Nov 2017 01:22:04 +0000 (UTC) Mathieu Desnoyers wrote: > > ----- On Nov 14, 2017, at 7:15 PM, Stephen Rothwell sfr@canb.auug.org.au wrote: > > > On Tue, 14 Nov 2017 23:54:06 +0000 (UTC) Mathieu Desnoyers > > wrote: > >> > >> Would it be possible to add the "rseq" tree to -next for testing ? > >> > >> I prepared a branch at: > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/rseq/linux-rseq.git > >> branch: rseq/for-next > > > > I try not to add new trees during the merge window (the only exceptions > > are for trees that will remain empty until after the merge window > > closes or trees only containing material for the current merge window - > > and in that case it is a bit late and a pain if it interacts with > > anything else). > > > > I will add it after -rc1 is released, though. Please remind me if I > > forget. > > No worries, sorry for the short notice. I'll try to do a merge > attempt into -next on my end before sending to Linus then. OK, since you intend to ask Linus to merge it during this merge window, I have added it from today (I hope I don't regret it too much :-)). 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