Hi John, > > Wanted to get your feedback on what you think would be the best > > approach to take for focus on development for Bluetooth 3.0 support. > > Hoping there is a better solution than using linux-next. > > I'm sure Marcel and Johannes are way ahead of us on this. :-) > > I think you covered the basics, but you did leave-out the possibility > of using net-next-2.6 for bleeding-edge development of bluetooth 3. > Since both Marcel and I feed Dave's tree and Dave endeavours to > keep the history of that tree stable then this would seem like your > best bet. if we reach the point where any kind of coordination is needed between your and my tree, I would just merge into wireless-next-2.6 tree instead of net-next-2.6. That should solve most issues around this anyway. And in case it doesn't we will always need manual interaction on one side. So I wouldn't try to overthink this right now. The only tricky part I see is wireless-testing since bluetooth-testing is not immutable right now. And I don't have any intention to make it that way. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
