From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756422AbdKOAPr (ORCPT ); Tue, 14 Nov 2017 19:15:47 -0500 Received: from ozlabs.org ([103.22.144.67]:33901 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753449AbdKOAPl (ORCPT ); Tue, 14 Nov 2017 19:15:41 -0500 Date: Wed, 15 Nov 2017 11:15:39 +1100 From: Stephen Rothwell To: Mathieu Desnoyers Cc: "Paul E. McKenney" , linux-kernel Subject: Re: Adding rseq tree to -next Message-ID: <20171115111539.68aa2539@canb.auug.org.au> In-Reply-To: <210317081.15258.1510703646315.JavaMail.zimbra@efficios.com> References: <210317081.15258.1510703646315.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 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. -- Cheers, Stephen Rothwell