tree addition request

tree addition request

[Ben Dooks]

Is this the right place to request adding one/two trees to linux-next?

git://git.fluff.org/bjdooks/linux.git next-i2c
git://git.fluff.org/bjdooks/linux.git next-samsung

thanks,
-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

Re: tree addition request

[Stephen Rothwell]

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

Hi Ben,

On Mon, 23 Nov 2009 22:30:44 +0000 Ben Dooks <ben-linux@fluff.org> wrote:
>
> Is this the right place to request adding one/two trees to linux-next?

Yep.

> git://git.fluff.org/bjdooks/linux.git next-i2c

I already have an i2c quilt series from Jean Delvare
<khali@linux-fr.org>, how does this relate to that?

> git://git.fluff.org/bjdooks/linux.git next-samsung

This is a set of arm platforms, right?

I have added both these trees from today, assuming there are no
objections.  I have called them bjdooks-i2c and sumsung respectively.

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

Re: tree addition request

[Jean Delvare]

Hi Stephen, Ben,

On Tue, 24 Nov 2009 10:51:14 +1100, Stephen Rothwell wrote:
> On Mon, 23 Nov 2009 22:30:44 +0000 Ben Dooks <ben-linux@fluff.org> wrote:
> > git://git.fluff.org/bjdooks/linux.git next-i2c

Ben, if this tree is somewhat official, please consider listing it in
MAINTAINERS.

> I already have an i2c quilt series from Jean Delvare
> <khali@linux-fr.org>, how does this relate to that?

Ben and me co-maintain the i2c subsystem. I take care of i2c-core and
PC driver, while Ben maintains the embedded platform drivers. There
should be no overlapping in our trees.

Ideally my tree would be included first, in case Ben has changes which
depend on i2c-core changes (which would belong to my tree). But I can't
remember such a case in the past, so I don't expect it to be frequent.

-- 
Jean Delvare

Re: tree addition request

[Stephen Rothwell]

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

Hi Jean,

On Tue, 24 Nov 2009 08:39:47 +0100 Jean Delvare <khali@linux-fr.org> wrote:
>
> Ben and me co-maintain the i2c subsystem. I take care of i2c-core and
> PC driver, while Ben maintains the embedded platform drivers. There
> should be no overlapping in our trees.

OK, thanks.  That is the case today.

> Ideally my tree would be included first, in case Ben has changes which
> depend on i2c-core changes (which would belong to my tree). But I can't
> remember such a case in the past, so I don't expect it to be frequent.

I have done that as well.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

Re: tree addition request

[Ben Dooks]

On Tue, Nov 24, 2009 at 10:51:14AM +1100, Stephen Rothwell wrote:
> Hi Ben,
> 
> On Mon, 23 Nov 2009 22:30:44 +0000 Ben Dooks <ben-linux@fluff.org> wrote:
> >
> > Is this the right place to request adding one/two trees to linux-next?
> 
> Yep.
> 
> > git://git.fluff.org/bjdooks/linux.git next-i2c
> 
> I already have an i2c quilt series from Jean Delvare
> <khali@linux-fr.org>, how does this relate to that?

I've been doing the more 'embedded' side of things, which means generally
the non-X86 side of things such as ARM, MIPS, etc. for the last couple of
releases.
 
> > git://git.fluff.org/bjdooks/linux.git next-samsung
> 
> This is a set of arm platforms, right?

This is the ARM support for a number of Samsung SoC/processors that
i've been maintaining for a long time now. A number of people have
requested these trees be included in -next now that the non-core ARM
code is being submitted directly to linus.
 
> I have added both these trees from today, assuming there are no
> objections.  I have called them bjdooks-i2c and sumsung respectively.
> 
> 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.

Yes.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.