Re: Build regressions/improvements in v5.3-rc4

[Randy Dunlap <rdunlap@infradead.org>]

On 8/12/19 2:09 PM, Geert Uytterhoeven wrote:
> Hi Randy,
> 
> On Mon, Aug 12, 2019 at 10:34 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 8/12/19 3:20 AM, Geert Uytterhoeven wrote:
>>> Below is the list of build error/warning regressions/improvements in
>>> v5.3-rc4[1] compared to v5.2[2].
>>>
>>> Summarized:
>>>   - build errors: +5/-1
>>>   - build warnings: +137/-136
>>>
>>> JFYI, when comparing v5.3-rc4[1] to v5.3-rc3[3], the summaries are:
>>>   - build errors: +0/-4
>>>   - build warnings: +105/-69
>>>
>>> Happy fixing! ;-)
>>>
>>> Thanks to the linux-next team for providing the build service.
>>>
>>> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/d45331b00ddb179e291766617259261c112db872/ (all 242 configs)
>>> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/0ecfebd2b52404ae0c54a878c872bb93363ada36/ (all 242 configs)
>>> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/e21a712a9685488f5ce80495b37b9fdbe96c230d/ (all 242 configs)
>>
>>
>>> *** WARNINGS ***
>>>
>>> 137 warning regressions:
>>
>>>   + warning: unmet direct dependencies detected for MTD_COMPLEX_MAPPINGS:  => N/A
> 
> WARNING: unmet direct dependencies detected for MTD_COMPLEX_MAPPINGS:
> 8 warnings in 2 logs
>         v5.3-rc4/um-x86_64/um-allyesconfig v5.3-rc4/um-x86_64/um-allmodconfig

Thanks.  I sent patches for 2 drivers that should depend on HAS_IOMEM.

>> It would be Really Good if there was some automated way to know which
>> of the 242 configs this is from (instead of you having to grep and reply to
>> email or someone/me having to download up to 242 log files).
> 
> I used to upload the summary containing that info to kernel.org. Then they
> made kup mandatory, and during the last 7 years, I still haven't looked into
> mastering kup. Ugh...

Ack and ditto here.

-- 
~Randy