On Sat, Oct 8, 2011 at 12:01 AM, Jeff Kirsher <tarbal@xxxxxxxxx> wrote: > On 10/07/2011 11:55 PM, Yinglin Sun wrote: >> On Fri, Oct 7, 2011 at 12:59 PM, David Miller <davem@xxxxxxxxxxxxx> wrote: >>> From: David Miller <davem@xxxxxxxxxxxxx> >>> Date: Fri, 07 Oct 2011 14:57:03 -0400 (EDT) >>> >>>> I'm about to setup my GIT trees on kernel.org, once that is complete >>>> I will be solely updating those trees again. >>>> >>>> I will notify everyone when this is ready to go. >>>> >>>> Just a heads up for everyone... >>> Ok, they are now online, please update your URLs. >>> >>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git >>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git >>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc.git >>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide.git >>> >> I'm still new to net kernel development, so a little confused about these trees. >> So we should submit patches based on these trees, instead of Linus'? >> About net and net-next, How to decide which one to use? >> >> Thanks! >> >> Yinglin >> > > *If* you have change against the network core/drivers then, you would > want to use David Miller's net or net-next trees. > > As a general rule: > - net tree is only for fixes/critical fixes > - net-next tree is for everything else > > There are always exceptions, but if you stick to the above general rule, > you will be fine. > > Got it. Thanks Jeff! Yinglin -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
