Re: ftrace next tree request

Re: ftrace next tree request

[Stephen Rothwell]

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

Hi Steve,

On Mon, 12 Nov 2012 13:45:34 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Here's my request for getting the ftrace tree into next.
> 
> Git repo: 
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> 
> Branch: for-next
> 
> Name: ftrace
> 
> Contact: rostedt@goodmis.org

As this seems to be based on things in the tip tree, I have positioned it
after that tree.

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: 836 bytes --]

Re: ftrace next tree request

[Steven Rostedt]

On Tue, 2012-11-13 at 08:47 +1100, Stephen Rothwell wrote:

> As this seems to be based on things in the tip tree, I have positioned it
> after that tree.

Yes it is. Sorry I should have reported that. But as Ingo hasn't been
seen since Oct 30th (I think he's on vacation), and my code is just
sitting in limbo on LKML, I figured I start getting it tested for 3.8, 
and not wait for Ingo to pull it into tip.

I plan on doing this for other releases too.

Thanks!

-- Steve

Re: ftrace next tree request

[Stephen Rothwell]

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

Hi Steve,

On Mon, 12 Nov 2012 16:52:56 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Tue, 2012-11-13 at 08:47 +1100, Stephen Rothwell wrote:
> 
> > As this seems to be based on things in the tip tree, I have positioned it
> > after that tree.
> 
> Yes it is. Sorry I should have reported that. But as Ingo hasn't been
> seen since Oct 30th (I think he's on vacation), and my code is just
> sitting in limbo on LKML, I figured I start getting it tested for 3.8, 
> and not wait for Ingo to pull it into tip.
> 
> I plan on doing this for other releases too.

Not a problem.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]