linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Adding hwspinlock-next to linux-next
@ 2011-09-21 17:22 Ohad Ben-Cohen
  2011-09-22  1:18 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Ohad Ben-Cohen @ 2011-09-21 17:22 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-kernel, linux-next

Hi Stephen,

Can you please add the following hwspinlock tree to linux-next ?

git://github.com/ohadbc/hwspinlock-next.git linux-next

(I'll most likely switch to kernel.org once it's up again)

Thanks!
Ohad.

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

* Re: Adding hwspinlock-next to linux-next
  2011-09-21 17:22 Adding hwspinlock-next to linux-next Ohad Ben-Cohen
@ 2011-09-22  1:18 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2011-09-22  1:18 UTC (permalink / raw)
  To: Ohad Ben-Cohen; +Cc: linux-kernel, linux-next

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

Hi Ohad,

On Wed, 21 Sep 2011 20:22:56 +0300 Ohad Ben-Cohen <ohad@wizery.com> wrote:
>
> Can you please add the following hwspinlock tree to linux-next ?
> 
> git://github.com/ohadbc/hwspinlock-next.git linux-next

I have added that from today.

> (I'll most likely switch to kernel.org once it's up again)

Understood.

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: 490 bytes --]

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

end of thread, other threads:[~2011-09-22  1:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-21 17:22 Adding hwspinlock-next to linux-next Ohad Ben-Cohen
2011-09-22  1:18 ` Stephen Rothwell

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).