Prev: mm,migration: During fork(), wait for migration to end if migration PTE is encountered
Next: [Patch 1/1] init: Increase pid_max based on num_possible_cpus v4
From: Greg KH on 26 Apr 2010 20:10
Hi,

Welcome back from your break :)

Could you include a new git tree in linux-next, the staging-next tree
at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-next-2.6.git

the branch is "staging-next" to pull from.

I'm trying to do the -next work for staging in a git tree to keep my
development quilt trees smaller, and make it a bit easier for others to
work off of if they want to.

If I've messed anything up, please let me know.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Rothwell on 26 Apr 2010 23:30
Hi Greg,

On Mon, 26 Apr 2010 17:01:04 -0700 Greg KH <greg(a)kroah.com> wrote:
>
> Welcome back from your break :)

Thanks - I was nice and refreshed until about 9am this morning :-)

> Could you include a new git tree in linux-next, the staging-next tree
> at:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-next-2.6.git
>
> the branch is "staging-next" to pull from.

OK, I will add it at the end today. I assume that this will be based off
Linus' tree?

> I'm trying to do the -next work for staging in a git tree to keep my
> development quilt trees smaller, and make it a bit easier for others to
> work off of if they want to.

Should I drop the "staging" quilt tree?

> If I've messed anything up, please let me know.

You'll hear the screams :-)

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(a)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.
 | 
Pages: 1
Prev: mm,migration: During fork(), wait for migration to end if migration PTE is encountered
Next: [Patch 1/1] init: Increase pid_max based on num_possible_cpus v4