Igor Mitsyanko <igor.mitsyanko.os@xxxxxxxxxxxxx> writes: > I applied this to the pending branch so that kbuild bot can run build tests on > it. Let's see what it finds. > > > > Kalle, I think you did that before already, at least I have received a > following error report a while back: > > > Hi, > > [auto build test ERROR on wireless-drivers-next/master] > [also build test ERROR on v4.7-rc4 next-20160620] > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > url: https://github.com/0day-ci/linux/commits/igor-mitsyanko-os-quantenna-com/qtnfmac-announcement-of-new-FullMAC-driver-for-Quantenna-chipsets/20160621-061419 > base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master > config: m32r-allyesconfig (attached as .config) > compiler: m32r-linux-gcc (GCC) 4.9.0 > reproduce: > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # save the attached .config to linux build tree > make.cross ARCH=m32r I suspect that in this case the kbuild bot took the patch from the mailing list and run some quick tests on that. But AFAIK commits on a git tree get wider testing. -- 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
