New tree to be added on linux-next

New tree to be added on linux-next

[Mauro Carvalho Chehab]

Hi Stephen,

Please add the edac.git tree to linux-next:

ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/edac.git linux_next

It currently contains a new driver for i7300_edac.

Thanks,
Mauro

Re: New tree to be added on linux-next

[Stephen Rothwell]

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

Hi Mauro,

On Wed, 22 Sep 2010 09:52:09 -0300 Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>
> Please add the edac.git tree to linux-next:
> 
> ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/edac.git linux_next
> 
> It currently contains a new driver for i7300_edac.

Added from today.  I called it i7300_edac (I now have 3 edac trees, this
one, i7core_edac and edac-amd).

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: New tree to be added on linux-next

[Mauro Carvalho Chehab]

Em 22-09-2010 19:34, Stephen Rothwell escreveu:
> Hi Mauro,
> 
> On Wed, 22 Sep 2010 09:52:09 -0300 Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>>
>> Please add the edac.git tree to linux-next:
>>
>> ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/edac.git linux_next
>>
>> It currently contains a new driver for i7300_edac.
> 
> Added from today.  I called it i7300_edac (I now have 3 edac trees, this
> one, i7core_edac and edac-amd).

Thank you! For its current contents, calling it as i7300_edac seems ok.
> 
> 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.
>