linux-kernel - Re: linux-next: removal of the rpmsg tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK=WgbaDinH5VC+tP5NYZMbh7CiOSfqNbkZEbaN3cT5pZhae5g@mail.gmail.com>
Date:	Wed, 9 Mar 2016 17:07:33 +0200
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: linux-next: removal of the rpmsg tree

Hi Stephen,

On Wed, Mar 9, 2016 at 7:28 AM, Stephen Rothwell <sfr@...b.auug.org.au> 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 a lot,
Ohad.