All of lore.kernel.org
 help / color / mirror / Atom feed
* Renesas linux-next tree
@ 2012-08-27  7:36 Rafael J. Wysocki
  2012-09-03 23:58 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Rafael J. Wysocki @ 2012-08-27  7:36 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, Simon Horman, Magnus Damm

Hi Stephen,

Since the Renesas arm/mach-shmobile tree will be maintained by
Simon Horman now, please stop pulling from the 'next' branch
of my 'renesas.git' tree at:

git://git.kernel.org/pub/scm/linux/kernel/git/rafael/renesas.git next

and please include the Simon's tree at:

git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next

into linux-next instead.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Renesas linux-next tree
  2012-08-27  7:36 Renesas linux-next tree Rafael J. Wysocki
@ 2012-09-03 23:58 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2012-09-03 23:58 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: linux-next, Simon Horman, Magnus Damm

[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]

Hi Rafael,

On Mon, 27 Aug 2012 09:36:09 +0200 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> Since the Renesas arm/mach-shmobile tree will be maintained by
> Simon Horman now, please stop pulling from the 'next' branch
> of my 'renesas.git' tree at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/renesas.git next
> 
> and please include the Simon's tree at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
> 
> into linux-next instead.

I have changed that from today and set Simon as the contact person for
problems.

This is for Simon:

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@canb.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.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-09-03 23:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-27  7:36 Renesas linux-next tree Rafael J. Wysocki
2012-09-03 23:58 ` Stephen Rothwell

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.