xilinx linux-next tree addition request

xilinx linux-next tree addition request

[John Linn]

Hi Stephen,

I have a tree I'd like to see show up in linux-next: 

git://git.xilinx.com/linux-2.6-xlnx.git arm-next 

After v2.6.39-rc1 is released, it will contain Xilinx ARM work intended
for the 2.6.40 merge window.  Everything in there has been posted,
reviewed, fixed, etc...

If order makes a difference, it would be best if it's after Russell's
tree as it could have dependencies on stuff in his tree.

It is only Linus's linux-2.6 tree right now, but I wanted to get this
all staged up and ready.

Thanks,
John   





This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

Re: xilinx linux-next tree addition request

[Stephen Rothwell]

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

Hi John,

On Fri, 25 Mar 2011 14:35:12 -0600 John Linn <John.Linn@xilinx.com> wrote:
>
> I have a tree I'd like to see show up in linux-next: 
> 
> git://git.xilinx.com/linux-2.6-xlnx.git arm-next 
> 
> After v2.6.39-rc1 is released, it will contain Xilinx ARM work intended
> for the 2.6.40 merge window.  Everything in there has been posted,
> reviewed, fixed, etc...
> 
> If order makes a difference, it would be best if it's after Russell's
> tree as it could have dependencies on stuff in his tree.

This will be added from today (I was waiting for -rc1).  I have put you
down as the contact, if you want any additional people/lists, then just
let me know.

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 --]

RE: xilinx linux-next tree addition request

[John Linn]

> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Tuesday, March 29, 2011 5:14 PM
> To: John Linn
> Cc: linux-next@vger.kernel.org; LKML; grant.likely@secretlab.ca
> Subject: Re: xilinx linux-next tree addition request
> 
> Hi John,
> 
> On Fri, 25 Mar 2011 14:35:12 -0600 John Linn <John.Linn@xilinx.com>
> wrote:
> >
> > I have a tree I'd like to see show up in linux-next:
> >
> > git://git.xilinx.com/linux-2.6-xlnx.git arm-next
> >
> > After v2.6.39-rc1 is released, it will contain Xilinx ARM work
> > intended for the 2.6.40 merge window.  Everything in there has been
> > posted, reviewed, fixed, etc...
> >
> > If order makes a difference, it would be best if it's after
Russell's
> > tree as it could have dependencies on stuff in his tree.
> 
> This will be added from today (I was waiting for -rc1).  I have put
you
> down as the contact, if you want any additional people/lists, then
just
> let me know.

Great, appreciate the help.

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

Of course, agreed.

Thanks,
John

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

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.