mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* please pull "idle-test" branch into linux-next
@ 2010-05-27  2:35 Len Brown
  2010-05-27  3:08 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Len Brown @ 2010-05-27  2:35 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linux Power Management List, linux-acpi, Linux Kernel Mailing List

Hi Stephen,

The idle patches currently in linux-acpi are unrelated to ACPI,
so I'm moving them to a new home.  Please add the new home
to your linux-next pull list:

git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-idle-2.6.git idle-test

thanks,
Len Brown, Intel Open Source Technology Center

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: please pull "idle-test" branch into linux-next
  2010-05-27  2:35 please pull "idle-test" branch into linux-next Len Brown
@ 2010-05-27  3:08 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2010-05-27  3:08 UTC (permalink / raw)
  To: Len Brown
  Cc: Linux Power Management List, linux-acpi, Linux Kernel Mailing List

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

Hi Len,

On Wed, 26 May 2010 22:35:52 -0400 (EDT) Len Brown <lenb@kernel.org> wrote:
>
> The idle patches currently in linux-acpi are unrelated to ACPI,
> so I'm moving them to a new home.  Please add the new home
> to your linux-next pull list:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-idle-2.6.git idle-test

I will add it tomorrow (assuming that it is for 2.6.35).

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-05-27  3:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-05-27  2:35 please pull "idle-test" branch into linux-next Len Brown
2010-05-27  3:08 ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®