Jaap Jan Meijer <jjmeijer88@xxxxxxxxx> writes: > 2016-05-06 17:02 GMT+01:00 Kalle Valo <kvalo@xxxxxxxxxxxxxx>: >> Jaap Jan Meijer <jjmeijer88@xxxxxxxxx> writes: >> >>> 2016-05-06 16:12 GMT+01:00 Kalle Valo <kvalo@xxxxxxxxxxxxxx>: >>>> Jaap Jan Meijer <jjmeijer88@xxxxxxxxx> writes: >>>> >>>>> I'm not sure what went wrong with the commit hash, its actually this commit: >>>>> 1f0dc59a6de93586fcfc04696a61946408ffc56a. >>>> >>>> That commit id looks to be valid. >>>> >>>>> I see you did this commit, maybe you can check if this actually is the root >>>>> cause? I'm sure you have a lot more insight into this issue than I do. >> >> I just commited the patch. Broadcom folks (CCed) should be able to >> answer better, most likely they missed this patch as the title didn't >> have "brcmfmac". > > Thanks, so no need to send a revised patch? Also, could you please > point me to the right repository so I can follow the progress? Sorry, I had very bad choise of words. I meant that I only commit patches (like the commit 1f0dc59a6d we are discussing here), I'm not familiar with brcmfmac internals. So I have NOT applied this patch and you need to send v2. I see that Arend also found some issues, please follow his advice. > Also, could you please point me to the right repository so I can > follow the progress? You can check that from MAINTAINERS file: NETWORKING DRIVERS (WIRELESS) M: Kalle Valo <kvalo@xxxxxxxxxxxxxx> L: linux-wireless@xxxxxxxxxxxxxxx Q: http://patchwork.kernel.org/project/linux-wireless/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git T: git git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git S: Maintained F: drivers/net/wireless/ But wireless-testing tree, maintained by Bob Copeland, is handy to follow the status because it contains all the wireless trees: https://git.kernel.org/cgit/linux/kernel/git/wireless/wireless-testing.git/ -- 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
