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/