From: Kalle Valo <kvalo@codeaurora.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.15-rc1
Date: Mon, 27 Nov 2017 14:57:37 +0200 [thread overview]
Message-ID: <87lgirx4ji.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CAMuHMdX6XpKbLYuwkdCK0YhYGaV5Sg8+v0DrUV9y6R3Qozf-qQ@mail.gmail.com> (Geert Uytterhoeven's message of "Mon, 27 Nov 2017 11:11:17 +0100")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> On Mon, Nov 27, 2017 at 11:01 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v4.15-rc1[1] compared to v4.14[2].
>>
>> Summarized:
>> - build errors: +2/-5
>
>> [1] http://kisskb.ellerman.id.au/kisskb/head/4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323/ (all 271 configs)
>> [2] http://kisskb.ellerman.id.au/kisskb/head/bebc6082da0a9f5d47a1ea2edc099bf671058bd4/ (270 out of 271 configs)
>
>> 2 error regressions:
>> + /home/kisskb/slave/src/drivers/gpu/drm/i915/intel_csr.c: error: 'si' may be used uninitialized in this function [-Werror=uninitialized]: => 204:3
>
> x86_64-randconfig
>
>> + /home/kisskb/slave/src/include/linux/bcma/bcma_driver_pci.h: error: field 'pci_controller' has incomplete type: => 218:24
The last "real" change to that file was from 2015 so I guess something
else changed to trigger this? But anyway, I guess the reason is missing
struct pci_controller forward declaration? Or missing include
<asm/pci-bridge.h? Not sure.
--
Kalle Valo
prev parent reply other threads:[~2017-11-27 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1511776877-11130-1-git-send-email-geert@linux-m68k.org>
2017-11-27 10:11 ` Build regressions/improvements in v4.15-rc1 Geert Uytterhoeven
2017-11-27 12:57 ` Kalle Valo [this message]
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=87lgirx4ji.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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