From: Thomas Zimmermann <tzimmermann@suse.de>
To: Nick Bowler <nbowler@draconx.ca>,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: PROBLEM: Linux 6.8 build failure in sun ffb driver (regression)
Date: Fri, 22 Mar 2024 09:21:57 +0100 [thread overview]
Message-ID: <4ed32e4f-d794-42ab-9292-cb6f11b31348@suse.de> (raw)
In-Reply-To: <7c9b4c27-e179-c136-e327-4c467ece81a2@draconx.ca>
Hi
Am 22.03.24 um 03:18 schrieb Nick Bowler:
> I bisected this build failure to the following commit:
>
> commit 8813e86f6d82a7931446c3cbc5d596f77d0f1ba6
> Author: Thomas Zimmermann <tzimmermann@suse.de>
> Date: Mon Nov 27 14:16:01 2023 +0100
>
> fbdev: Remove default file-I/O implementations
>
> If I revert this commit on top of 6.8, the build is successful.
Thanks for reporting. It looks like a trivial Kconfig problem. I'll send
a patch.
Best regards
Thomas
>
> On 2024-03-21 21:00, Nick Bowler wrote:
>> Hi,
>>
>> Linux 6.8 (and 6.8.1) are failing to build for me:
>>
>> LD .tmp_vmlinux.kallsyms1
>> sparc64-unknown-linux-gnu-ld: drivers/video/fbdev/ffb.o:(.rodata+0x270): undefined reference to `fb_io_read'
>> sparc64-unknown-linux-gnu-ld: drivers/video/fbdev/ffb.o:(.rodata+0x278): undefined reference to `fb_io_write'
>> make[3]: *** [/home/nbowler/misc/linux/scripts/Makefile.vmlinux:37: vmlinux] Error 1
>>
>> This problem does not occur when building Linux 6.7 which builds successfully.
>>
>> Kernel .config attached (gzipped).
>>
>> Please let me know if you need any more info.
>>
>> Thanks,
>> Nick
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
prev parent reply other threads:[~2024-03-22 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 1:00 Nick Bowler
2024-03-22 2:18 ` Nick Bowler
2024-03-22 8:21 ` Thomas Zimmermann [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=4ed32e4f-d794-42ab-9292-cb6f11b31348@suse.de \
--to=tzimmermann@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=regressions@lists.linux.dev \
--cc=sparclinux@vger.kernel.org \
/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®