Christian Eisendle wrote: >>> IMHO it would make sense to have 3 branches (BSP, USB, WiFi) each based >>> on >>> unmodified 2.6.22 Kernel. USB and WiFi branch is used for generating the >>> patch and for applying possible fixes. BSP branch for actual BSP related >>> feature development and fixes. >>> The changes in these branches are merged into the master branch which is >>> used for compiling/testing the whole BSP. >> >> Are you planning to submit these patches upstream at any point? If >> not, it might be easiest to just jam them all together in one branch >> and not look back. Since it seems like they probably affect quite >> different parts of the code, you could always extract a clean set of >> patches *later* and submit those patches upstream. > > For BSP I plan to upstream eventually. > > The basic idea was to divide the project in three different patches since > USB and WiFi comes from a third party and is not released under GPL (well, > different story...) Do you distribute this kernel? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html