linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: new arch/metag tree
@ 2013-01-29 14:30 James Hogan
  2013-01-29 20:51 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: James Hogan @ 2013-01-29 14:30 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-kernel, linux-arch, Arnd

Hi Stephen,

Please can you add the following branch to linux-next for Meta
architecture support:

git://github.com/jahogan/metag-linux.git for-next

(this is currently v4 of the patchset excluding the last two patches,
the tty and fs drivers, as I'd like acks first).

Thanks
James


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

* Re: linux-next: new arch/metag tree
  2013-01-29 14:30 linux-next: new arch/metag tree James Hogan
@ 2013-01-29 20:51 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2013-01-29 20:51 UTC (permalink / raw)
  To: James Hogan; +Cc: linux-kernel, linux-arch, Arnd

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

Hi James,

On Tue, 29 Jan 2013 14:30:52 +0000 James Hogan <james.hogan@imgtec.com> wrote:
>
> Please can you add the following branch to linux-next for Meta
> architecture support:
> 
> git://github.com/jahogan/metag-linux.git for-next

Added from today (though there may not be a linux-next release today).

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:[~2013-01-29 20:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-29 14:30 linux-next: new arch/metag tree James Hogan
2013-01-29 20:51 ` 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).