All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Please add my tree to linux-next
Date: Mon, 05 Dec 2011 13:40:29 +0800	[thread overview]
Message-ID: <4EDC594D.5040008@redhat.com> (raw)
In-Reply-To: <20111205100930.1bedc458a5e78b85c563465d@canb.auug.org.au>

于 2011年12月05日 07:09, Stephen Rothwell 写道:
> Hi,
>
> On Fri, 02 Dec 2011 12:22:54 +0800 Cong Wang<amwang@redhat.com>  wrote:
>>
>> As Andrew Morton suggested, please add my tree which contains all
>> of my patches for kmap_atomic() [1] to linux-next. Some of the
>> individual patches already got ACK from subsystem maintainers.
>> The tree is hosted on github:
>>
>>       git://github.com/congwang/linux.git #kmap_atomic
>
> I have added this tree to linux-next 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,

When I sent the patches out, they all have my Signed-off-by, but not in the
commit logs in my tree. Is this a problem?

>       * posted to the relevant mailing list,

Yes, see http://lkml.org/lkml/2011/11/27/2.

>       * reviewed by you (or another maintainer of your subsystem tree),

Yes.

>       * successfully unit tested, and

Yes, compile-tested on x86_64 and ppc.

>       * destined for the current or next Linux merge window.

Yes, for next 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.
>

Ok.

Thanks!

  reply	other threads:[~2011-12-05  5:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  4:22 Please add my tree to linux-next Cong Wang
2011-12-04 23:09 ` Stephen Rothwell
2011-12-05  5:40   ` Cong Wang [this message]
2011-12-05  6:12     ` Stephen Rothwell
2011-12-05  6:52       ` Cong Wang
2011-12-07  9:35         ` Cong Wang
2011-12-07 10:37           ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2013-10-31 19:39 Robert Richter
2013-10-31 22:35 ` Stephen Rothwell
2013-10-31 23:44   ` Robert Richter

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=4EDC594D.5040008@redhat.com \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@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.