LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for February 10
Date: Mon, 14 Feb 2011 10:16:53 +1100	[thread overview]
Message-ID: <20110214101653.1b159114.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.02.1102110000090.3384@x980>

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

Hi Len,

On Fri, 11 Feb 2011 00:05:25 -0500 (EST) Len Brown <lenb@kernel.org> wrote:
>
> Please add this branch
> 
> master.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-idle-2.6.git tools
> 
> It is a branch for the stuff in tools/power/

Added from 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: 490 bytes --]

  parent reply	other threads:[~2011-02-13 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  7:05 Stephen Rothwell
2011-02-10 17:52 ` linux-next: Tree for February 10 (netfilter) Randy Dunlap
2011-02-14  7:34   ` Patrick McHardy
2011-03-03 21:54     ` Randy Dunlap
2011-02-10 19:00 ` linux-next: Tree for February 10 (zcache) Randy Dunlap
2011-02-10 21:05   ` Nitin Gupta
     [not found] ` <alpine.LFD.2.02.1102110000090.3384@x980>
2011-02-13 23:16   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-10  6:55 linux-next: Tree for February 10 Stephen Rothwell
2009-02-10  8:41 Stephen Rothwell

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=20110214101653.1b159114.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --subject='Re: linux-next: Tree for February 10' \
    /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

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