Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> writes: >>>> I doubt that this will be in active enough development that a separate >>>> git tree is needed. wireless-drivers trees should be enough and this >>>> line can be removed. >>> >>> I would like to keep this line, it points to my development tree, which >>> allows users to go back and look through my full development logs, as >>> well as see ongoing work before it's pushed upstream. >> >> I prefer that wireless-drivers(-next).git is used as the baseline for >> wireless driver patches, so please remove this tag. You can document >> your git server in the wiki, commit log and so on. > > I will insist on keeping my branch listed as long as I maintain the > driver. Other drivers do the same thing, like iwlwifi. I'm happy to send > you patches against wireless-drivers-next.git though. To keep things simple for me I want that the patches are based on wireless-drivers-next.git. iwlwifi is under so active development that an extra tree is justified, but having a dedicated tree for a not so active driver is just extra work for me which I do not want to have. With rtlwifi it goes so that Larry acks the patches on the list and patchwork automatically adds the ack to the commit log when I apply the patch, which is easy and fast for everyone. The same should go with rtl8723au. -- Kalle Valo -- 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
