From: Javier Martinez Canillas <javierm@redhat.com>
To: Mark Brown <broonie@kernel.org>, Borislav Petkov <bp@suse.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: linux-next: build failure due to the drm tree
Date: Tue, 27 Jul 2021 00:08:23 +0200 [thread overview]
Message-ID: <d9bcb407-8ccd-aa42-46d7-c32cd0adcf89@redhat.com> (raw)
In-Reply-To: <20210726213600.4054-1-broonie@kernel.org>
Hello Mark,
On 7/26/21 11:36 PM, Mark Brown wrote:
> Hi all,
>
> Today's -next fails to build an arm64 allnoconfig:
>
> aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: in function `sysfb_init':
> sysfb.c:(.init.text+0xc): undefined reference to `screen_info'
> aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `screen_info' which may bind externally can not be used when making a shared object; recompile with -fPIC
> sysfb.c:(.init.text+0xc): dangerous relocation: unsupported relocation
> aarch64-none-linux-gnu-ld: sysfb.c:(.init.text+0x10): undefined reference to `screen_info'
> make[1]: *** [/tmp/next/build/Makefile:1276: vmlinux] Error 1
>
> Caused by
>
> d391c58271072d0b0f ("drivers/firmware: move x86 Generic System Framebuffers support")
>
Yes, this was already reported by the kernel test robot and posted a fix
a few days ago: https://lore.kernel.org/patchwork/patch/1465623/
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2021-07-26 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 21:36 linux-next: build failure due to the drm tree Mark Brown
2021-07-26 22:08 ` Javier Martinez Canillas [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=d9bcb407-8ccd-aa42-46d7-c32cd0adcf89@redhat.com \
--to=javierm@redhat.com \
--cc=bp@suse.de \
--cc=broonie@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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