Randy Dunlap <[email protected]> writes: > On 2/4/19 9:46 AM, Randy Dunlap wrote: >> On 2/4/19 5:42 AM, Geert Uytterhoeven wrote: >>> Below is the list of build error/warning regressions/improvements in >>> v5.0-rc5[1] compared to v4.20[2]. >>> >>> Summarized: >>> - build errors: +2/-4 >>> - build warnings: +113/-14843 >>> >>> JFYI, when comparing v5.0-rc5[1] to v5.0-rc4[3], the summaries are: >>> - build errors: +0/-0 >>> - build warnings: +56/-59 >>> >>> Note that there may be false regressions, as some logs are incomplete. >>> Still, they're build errors/warnings. >>> >>> Happy fixing! ;-) >>> >>> Thanks to the linux-next team for providing the build service. >>> >>> [1] >>> http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8834f5600cf3c8db365e18a3d5cac2c2780c81e5/ >>> (238 out of 240 configs) >>> [2] >>> http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8fe28cb58bcb235034b64cbbb7550a8a43fd88be/ >>> (all 240 configs) >>> [3] >>> http://kisskb.ellerman.id.au/kisskb/branch/linus/head/f17b5f06cb92ef2250513a1e154c47b78df07d40/ >>> (238 out of 240 configs) >>> >>> >>> >>> *** WARNINGS *** >>> >>> 113 warning regressions: >> >>> + warning: unmet direct dependencies detected for PPC4xx_PCI_EXPRESS: => >>> N/A >> >> Hi Geert, >> >> I am trying to find the above warning (needle) in the haystack. >> Can you please direct me to which config/build it is in? >> >> Is there a good way for me to find it? >> >> thanks. >> > > Working backwards, it probably comes from this: > > config CURRITUCK > bool "IBM Currituck (476fpe) Support" > depends on PPC_47x > select SWIOTLB > select 476FPE > select PPC4xx_PCI_EXPRESS > > This is the only similar Kconfig segment that does not select FORCE_PCI > but PPC4xx_PCI_EXPRESS depends on PCI but > # CONFIG_PCI is not set > > This could be related to a recent series of patches that allows ACPI to > be built without having PCI enabled. > > Michael?
There isn't really an easy way to do it sorry. If you download the page for the revision: http://kisskb.ellerman.id.au/kisskb/branch/linus/head/8834f5600cf3c8db365e18a3d5cac2c2780c81e5/ With a lot of grep/sed/awk you can get a list of the URLs for all the builds eg. one would be: http://kisskb.ellerman.id.au/kisskb/buildresult/13676551/ And then you can just tack on "log/" to get: http://kisskb.ellerman.id.au/kisskb/buildresult/13676551/log/ Which you can wget and grep. But that's all a bit of a pain. I have on my todo list to add json formatted build results and revision pages, which would make it quite a bit simpler. But of course I haven't had time to do it yet :/ cheers
