linux-kernel - Re: adding rpmsg.git to linux next

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] [day] [month] [year] [list]

Date:	Wed, 17 Apr 2013 10:02:33 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Ohad Ben-Cohen <ohad@...ery.com>
Cc:	"Tivy, Robert" <rtivy@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	linux-arm <linux-arm-kernel@...ts.infradead.org>
Subject: Re: adding rpmsg.git to linux next

Hi Ohad,

On Tue, 16 Apr 2013 20:51:13 +0300 Ohad Ben-Cohen <ohad@...ery.com> wrote:
>
> On Tue, Apr 16, 2013 at 3:07 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > On Mon, 15 Apr 2013 09:28:17 +0300 Ohad Ben-Cohen <ohad@...ery.com> wrote:
> >> Could you please add:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/rpmsg.git#for-next
> >>
> >> to linux-next to include new stuff coming from Rob?
> >
> > Well, you could tell me something about it.  Like what is in it and how
> > it will be merged up to Linus.  Does this have anything to do with the
> > remoteproc tree I already include?  Who is the official maintainer (there
> > is no mention of drivers/rpmsg in the MAINTAINERS file).
> 
> Sorry for not mentioning this.
> 
> This tree isn't new and is being used to send pull requests to Linus
> for some time. I guess that most (all?) of the pull requests contained
> fixes which needed no linux-next presence, so it never occurred to me
> the tree isn't part of linux-next.

All good, thanks for the explanation.  I have added that tree from today.

> commit d8115db52b99eefb99bcbf992edc349e691b4ca7
> Author: Ohad Ben-Cohen <ohad@...ery.com>
> Date:   Tue Apr 16 20:34:49 2013 +0300
> 
>     MAINTAINERS: add rpmsg entry
> 
>     People and scripts look for this.
> 
>     Signed-off-by: Ohad Ben-Cohen <ohad@...ery.com>

Good idea.

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@...b.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Content of type "application/pgp-signature" skipped