linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Ohad Ben-Cohen <ohad@wizery.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: removal of the rpmsg tree
Date: Wed, 9 Mar 2016 21:31:05 -0800	[thread overview]
Message-ID: <CAOCOHw4Y-iY+pOr4_L1zeDb6SES66_o=tBJy4wOD2ikgzMJPjg@mail.gmail.com> (raw)
In-Reply-To: <CAK=WgbaDinH5VC+tP5NYZMbh7CiOSfqNbkZEbaN3cT5pZhae5g@mail.gmail.com>

On Wed, Mar 9, 2016 at 7:07 AM, Ohad Ben-Cohen <ohad@wizery.com> wrote:
> Hi Stephen,
>
> On Wed, Mar 9, 2016 at 7:28 AM, Stephen Rothwell <sfr@canb.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 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

  reply	other threads:[~2016-03-10  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  5:28 linux-next: removal of the rpmsg tree Stephen Rothwell
2016-03-09 15:07 ` Ohad Ben-Cohen
2016-03-10  5:31   ` Bjorn Andersson [this message]
2016-03-10 20:48     ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOCOHw4Y-iY+pOr4_L1zeDb6SES66_o=tBJy4wOD2ikgzMJPjg@mail.gmail.com' \
    --to=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).