All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	Linux Edac Mailing List <linux-edac@vger.kernel.org>
Subject: Re: New tree to be added on linux-next
Date: Thu, 23 Sep 2010 02:02:08 -0300	[thread overview]
Message-ID: <4C9ADF50.60505@redhat.com> (raw)
In-Reply-To: <20100923083406.3c970103.sfr@canb.auug.org.au>

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

      reply	other threads:[~2010-09-23  5:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 12:52 New tree to be added on linux-next Mauro Carvalho Chehab
2010-09-22 22:34 ` Stephen Rothwell
2010-09-23  5:02   ` Mauro Carvalho Chehab [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C9ADF50.60505@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.