From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935111AbcCJFbJ (ORCPT ); Thu, 10 Mar 2016 00:31:09 -0500 Received: from mail-oi0-f49.google.com ([209.85.218.49]:35586 "EHLO mail-oi0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932906AbcCJFbG (ORCPT ); Thu, 10 Mar 2016 00:31:06 -0500 MIME-Version: 1.0 In-Reply-To: References: <20160309162826.60d6b72b@canb.auug.org.au> Date: Wed, 9 Mar 2016 21:31:05 -0800 Message-ID: Subject: Re: linux-next: removal of the rpmsg tree From: Bjorn Andersson To: Ohad Ben-Cohen , Stephen Rothwell Cc: linux-next@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 9, 2016 at 7:07 AM, Ohad Ben-Cohen wrote: > Hi Stephen, > > On Wed, Mar 9, 2016 at 7:28 AM, Stephen Rothwell wrote: >> Hi Ohad, >> >> I noticed that the rpmsg tree >> >> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/rpmsg.git branch for-next >> >> has not been updated since November 2014. I am going to remove it from >> linux-next tomorrow unless I hear that it may be useful. It can always >> be easily added back if it proves useful in the future. > > That should be fine. > > FWIW, Bjorn will most likely setup another rpmsg tree and ask you to > add it to linux-next, as he's co-maintaining > remoteproc/rpmsg/hwspinlock now. > Thanks for the poke. 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 I will let you know when we have patches in hwspinlock and rpmsg to set those up as well, but at the moment we don't have anything incoming there. Regards, Bjorn