Re: Another tree for "next"
Stephen Rothwell writes: >> >>> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: >> >>> next > OK, I have added your tree from today. Thanks a lot. -- Krzysztof Halasa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Another tree for next
Stephen Rothwell s...@canb.auug.org.au writes: git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next OK, I have added your tree from today. Thanks a lot. -- Krzysztof Halasa -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Another tree for "next"
Hi Krzysztof, On Mon, 10 Sep 2012 11:52:14 -0600 Stephen Warren wrote: > > On 09/10/2012 11:42 AM, Krzysztof Halasa wrote: > > Stephen Rothwell writes: > > > >>> could you please add the following to your "next" tree? > >>> > >>> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: > >>> next > > > >> Could you be a bit more clear about what will be in that tree, please? > >> Also when you repost this request, please post it a bit more widely among > >> other people/lists who may be interested in this work. Remember that > >> linux-next is really only for stuff that is ready for Linus to pull into > >> the next merge window (or bug fixes). Also, would this tree be pulled > >> directly by Linus, or via some other tree? > > > > My plan is to merge all the stuff I'm (eventually) working on in the > > above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to > > Linus > > ARM-SoC-related pull requests should be sent to the arm-soc tree, who > will then aggregate all the ARM-SoC-related changes and issue pull > requests to Linus. > > That is, a...@kernel.org, plus the Linux ARM kernel list CC'd. > > The patches would also need to be sent to the Linux ARM kernel list (and > any other relevant lists) before being applied to your tree. > > ARM core changes would likely go through Russell King's tree, perhaps > depending on what dependencies they have. OK, I have added your tree 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 s...@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. pgphqt38OC7RP.pgp Description: PGP signature
Re: Another tree for "next"
On 09/10/2012 11:42 AM, Krzysztof Halasa wrote: > Stephen Rothwell writes: > >>> could you please add the following to your "next" tree? >>> >>> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next > >> Could you be a bit more clear about what will be in that tree, please? >> Also when you repost this request, please post it a bit more widely among >> other people/lists who may be interested in this work. Remember that >> linux-next is really only for stuff that is ready for Linus to pull into >> the next merge window (or bug fixes). Also, would this tree be pulled >> directly by Linus, or via some other tree? > > My plan is to merge all the stuff I'm (eventually) working on in the > above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to > Linus ARM-SoC-related pull requests should be sent to the arm-soc tree, who will then aggregate all the ARM-SoC-related changes and issue pull requests to Linus. That is, a...@kernel.org, plus the Linux ARM kernel list CC'd. The patches would also need to be sent to the Linux ARM kernel list (and any other relevant lists) before being applied to your tree. ARM core changes would likely go through Russell King's tree, perhaps depending on what dependencies they have. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Another tree for "next"
Stephen Rothwell writes: >> could you please add the following to your "next" tree? >> >> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next > Could you be a bit more clear about what will be in that tree, please? > Also when you repost this request, please post it a bit more widely among > other people/lists who may be interested in this work. Remember that > linux-next is really only for stuff that is ready for Linus to pull into > the next merge window (or bug fixes). Also, would this tree be pulled > directly by Linus, or via some other tree? My plan is to merge all the stuff I'm (eventually) working on in the above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to Linus, and (from time to time) WAN network drivers pulled by Dave. BTW this includes both current fixes (for "this") and true "next" changes. All of this is low profile and will be frequently empty. Hope that's ok. Alternatively I can add separate trees/branches (currently I'm only working on IXP4xx, at least as far as we're talking about pullable git trees). Just wanted to minimize effort needed on your side. Not sure about these other people/lists, added lkml. -- Krzysztof Halasa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Another tree for next
Stephen Rothwell s...@canb.auug.org.au writes: could you please add the following to your next tree? git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next Could you be a bit more clear about what will be in that tree, please? Also when you repost this request, please post it a bit more widely among other people/lists who may be interested in this work. Remember that linux-next is really only for stuff that is ready for Linus to pull into the next merge window (or bug fixes). Also, would this tree be pulled directly by Linus, or via some other tree? My plan is to merge all the stuff I'm (eventually) working on in the above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to Linus, and (from time to time) WAN network drivers pulled by Dave. BTW this includes both current fixes (for this) and true next changes. All of this is low profile and will be frequently empty. Hope that's ok. Alternatively I can add separate trees/branches (currently I'm only working on IXP4xx, at least as far as we're talking about pullable git trees). Just wanted to minimize effort needed on your side. Not sure about these other people/lists, added lkml. -- Krzysztof Halasa -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Another tree for next
On 09/10/2012 11:42 AM, Krzysztof Halasa wrote: Stephen Rothwell s...@canb.auug.org.au writes: could you please add the following to your next tree? git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next Could you be a bit more clear about what will be in that tree, please? Also when you repost this request, please post it a bit more widely among other people/lists who may be interested in this work. Remember that linux-next is really only for stuff that is ready for Linus to pull into the next merge window (or bug fixes). Also, would this tree be pulled directly by Linus, or via some other tree? My plan is to merge all the stuff I'm (eventually) working on in the above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to Linus ARM-SoC-related pull requests should be sent to the arm-soc tree, who will then aggregate all the ARM-SoC-related changes and issue pull requests to Linus. That is, a...@kernel.org, plus the Linux ARM kernel list CC'd. The patches would also need to be sent to the Linux ARM kernel list (and any other relevant lists) before being applied to your tree. ARM core changes would likely go through Russell King's tree, perhaps depending on what dependencies they have. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Another tree for next
Hi Krzysztof, On Mon, 10 Sep 2012 11:52:14 -0600 Stephen Warren swar...@wwwdotorg.org wrote: On 09/10/2012 11:42 AM, Krzysztof Halasa wrote: Stephen Rothwell s...@canb.auug.org.au writes: could you please add the following to your next tree? git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next Could you be a bit more clear about what will be in that tree, please? Also when you repost this request, please post it a bit more widely among other people/lists who may be interested in this work. Remember that linux-next is really only for stuff that is ready for Linus to pull into the next merge window (or bug fixes). Also, would this tree be pulled directly by Linus, or via some other tree? My plan is to merge all the stuff I'm (eventually) working on in the above tree. For now - mostly IXP4xx (ARM CPU etc.) stuff which goes to Linus ARM-SoC-related pull requests should be sent to the arm-soc tree, who will then aggregate all the ARM-SoC-related changes and issue pull requests to Linus. That is, a...@kernel.org, plus the Linux ARM kernel list CC'd. The patches would also need to be sent to the Linux ARM kernel list (and any other relevant lists) before being applied to your tree. ARM core changes would likely go through Russell King's tree, perhaps depending on what dependencies they have. OK, I have added your tree 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 s...@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. pgphqt38OC7RP.pgp Description: PGP signature
