adding rpmsg.git to linux next

Commit Message

Ohad Ben Cohen April 16, 2013, 5:51 p.m. UTC

Hi Stephen,

On Tue, Apr 16, 2013 at 3:07 AM, Stephen Rothwell <[e-mail]> wrote:
> On Mon, 15 Apr 2013 09:28:17 +0300 Ohad Ben-Cohen <[e-mail]> 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.

Some background:

Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
with entities running on remote processors available on the system. In
turn, drivers could then
expose appropriate user space interfaces, if needed.

Rpmsg is essentially a multiplexer providing communication channels
which rpmsg drivers utilizes; it does not handle the physical state of
the remote processor, and in fact is completely decoupled from
remoteproc, which does focus on the physical state of the remote
processor (but has no communications aspect). For much more
information, please see Documentation/rpmsg.txt.

I maintain rpmsg (by sending pull requests to Linus), and for some
reason never added a MAINTAINERS entry for it. I can fix that quite
easily, let me know if this helps:

commit d8115db52b99eefb99bcbf992edc349e691b4ca7
Author: Ohad Ben-Cohen <[e-mail]>
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 <[e-mail]>


Hope this all helps, please let me know if anything else is needed.

Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [e-mail]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Comments

Stephen Rothwell April 17, 2013, 12:02 a.m. UTC | #1

Hi Ohad,

On Tue, 16 Apr 2013 20:51:13 +0300 Ohad Ben-Cohen <[e-mail]> wrote:
>
> On Tue, Apr 16, 2013 at 3:07 AM, Stephen Rothwell <[e-mail]> wrote:
> > On Mon, 15 Apr 2013 09:28:17 +0300 Ohad Ben-Cohen <[e-mail]> 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 <[e-mail]>
> 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 <[e-mail]>

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.

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index 9561658..eaca6c8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6604,6 +6604,14 @@  F:       drivers/remoteproc/
 F:     Documentation/remoteproc.txt
 F:     include/linux/remoteproc.h

+REMOTE PROCESSOR MESSAGING (RPMSG) SUBSYSTEM
+M:     Ohad Ben-Cohen <[e-mail]>
+T:     git git://git.kernel.org/pub/scm/linux/kernel/git/ohad/rpmsg.git
+S:     Maintained
+F:     drivers/rpmsg/
+F:     Documentation/rpmsg.txt
+F:     include/linux/rpmsg.h
+
 RFKILL
 M:     Johannes Berg <[e-mail]>
 L:     [e-mail]