Please add my tree to linux-next
Hi Stephen,
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 already rebased it to today's Linus tree.
Please let me know if I need to do anything else.
Thanks!
Hi,
Quoted 7 lines · On Fri, 02 Dec 2011 12:22:54 +0800 Cong Wang <[email protected]> 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,
* 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.
Signature · 15 lines
Cheers, Stephen Rothwell [email protected] 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.
Quoted 18 lines · Stephen Rothwell
Hi,
Quoted 7 lines · On Fri, 02 Dec 2011 12:22:54 +0800 Cong Wang<[email protected]> 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_atomicI 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.
Quoted 4 lines
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?
Quoted 1 line
* posted to the relevant mailing list,
Yes, see http://lkml.org/lkml/2011/11/27/2.
Quoted 1 line
* reviewed by you (or another maintainer of your subsystem tree),
Yes.
Quoted 1 line
* successfully unit tested, and
Yes, compile-tested on x86_64 and ppc.
Quoted 1 line
* destined for the current or next Linux merge window.
Yes, for next merge window.
Quoted 4 lines
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!
Hi,
Quoted 6 lines · On Mon, 05 Dec 2011 13:40:29 +0800 Cong Wang <[email protected]> wrote:
Quoted 3 lines
* 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?
Yes, you must have a signed-off-by line for each person who handles the patches (in this case just you, since you are also the author). Linus (in theory) would not merge your tree if you asked him to if it lacked signed-off-by lines (and I will have to drop it if they are not added - this will mean rebasing your tree, of course).
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Quoted 6 lines · Stephen Rothwell
Hi,
Quoted 4 lines · On Mon, 05 Dec 2011 13:40:29 +0800 Cong Wang<[email protected]> wrote:
Quoted 3 lines
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
Quoted 9 lines
Quoted 2 lines
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?
Yes, you must have a signed-off-by line for each person who handles the patches (in this case just you, since you are also the author). Linus (in theory) would not merge your tree if you asked him to if it lacked signed-off-by lines (and I will have to drop it if they are not added - this will mean rebasing your tree, of course).
Ok, I will re-commit those patches with my S-o-b and rebase my tree.
Thanks!
Hi, Stephen,
I just re-commit those patches into my tree with ACK's I got, and squash a patch which fixes ARM build, so it is rebased now. Please re-add it to linux-next.
git://github.com/congwang/linux.git #kmap_atomic
Thanks!
Hi,
Quoted 4 lines · On Wed, 07 Dec 2011 17:35:03 +0800 Cong Wang <[email protected]> wrote:
I just re-commit those patches into my tree with ACK's I got, and squash a patch which fixes ARM build, so it is rebased now. Please re-add it to linux-next.
You don't need to ask me to re-add your tree. As long as the URL and branch remain the same, I will attempt to fetch it each morning.
So the new contents will appear in tomorrow's linux-next,
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/