From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932185AbcCJUsL (ORCPT ); Thu, 10 Mar 2016 15:48:11 -0500 Received: from ozlabs.org ([103.22.144.67]:60322 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752795AbcCJUsI (ORCPT ); Thu, 10 Mar 2016 15:48:08 -0500 Date: Fri, 11 Mar 2016 07:48:06 +1100 From: Stephen Rothwell To: Bjorn Andersson Cc: Ohad Ben-Cohen , linux-next@vger.kernel.org, "linux-kernel@vger.kernel.org" Subject: Re: linux-next: removal of the rpmsg tree Message-ID: <20160311074806.40d34cce@canb.auug.org.au> In-Reply-To: References: <20160309162826.60d6b72b@canb.auug.org.au> 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 Bjorn, On Wed, 9 Mar 2016 21:31:05 -0800 Bjorn Andersson wrote: > > Stephen, I'm co-maintain the hwspinlock, rpmsg and remoteproc > subsystems; and will as such maintain the next branches. > > Could you please pull the remoteproc next patches from the "for-next" branch of: > git://github.com/andersson/remoteproc.git Added from today. Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment 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