From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: Build regressions/improvements in v5.0-rc5
Date: Mon, 4 Feb 2019 09:57:00 -0800 [thread overview]
Message-ID: <5ccff302-3986-5892-d072-5c334484f990@infradead.org> (raw)
In-Reply-To: <33e58393-97f1-321e-5ee0-a1242c7c7a26@infradead.org>
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?
--
~Randy
next prev parent reply other threads:[~2019-02-04 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 13:42 Geert Uytterhoeven
2019-02-04 17:46 ` Randy Dunlap
2019-02-04 17:57 ` Randy Dunlap [this message]
2019-02-04 17:58 ` Geert Uytterhoeven
2019-02-06 10:05 ` Michael Ellerman
2019-02-06 20:57 ` Randy Dunlap
2019-02-07 2:47 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ccff302-3986-5892-d072-5c334484f990@infradead.org \
--to=rdunlap@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®