public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Helge Deller" <deller@gmx.de>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the fbdev tree
Date: Sun, 8 Feb 2026 23:44:06 +0000	[thread overview]
Message-ID: <aYkfxvZGxTwUTQfK@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

Hi all,

After merging the fbdev tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

x86_64-linux-gnu-ld: vmlinux.o: in function `au1100fb_drv_remove':
au1100fb.c:(.text+0x251e220): undefined reference to `unregister_framebuffer'
x86_64-linux-gnu-ld: au1100fb.c:(.text+0x251e22c): undefined reference to `fb_dealloc_cmap'
x86_64-linux-gnu-ld: vmlinux.o: in function `au1100fb_setup':
au1100fb.c:(.text+0x251ec0f): undefined reference to `fb_get_options'
x86_64-linux-gnu-ld: vmlinux.o: in function `au1100fb_drv_probe':
au1100fb.c:(.text+0x252096f): undefined reference to `fb_alloc_cmap'
x86_64-linux-gnu-ld: au1100fb.c:(.text+0x2520997): undefined reference to `register_framebuffer'
x86_64-linux-gnu-ld: au1100fb.c:(.text+0x2520c08): undefined reference to `fb_dealloc_cmap'
x86_64-linux-gnu-ld: vmlinux.o: in function `BSWAP_SHUFB_CTL':
sha1-avx2-asm.o:(.rodata+0xc38498): undefined reference to `fb_io_read'
x86_64-linux-gnu-ld: sha1-avx2-asm.o:(.rodata+0xc384a0): undefined reference to `fb_io_write'
x86_64-linux-gnu-ld: sha1-avx2-asm.o:(.rodata+0xc384d8): undefined reference to `cfb_fillrect'
x86_64-linux-gnu-ld: sha1-avx2-asm.o:(.rodata+0xc384e0): undefined reference to `cfb_copyarea'
x86_64-linux-gnu-ld: sha1-avx2-asm.o:(.rodata+0xc384e8): undefined reference to `cfb_imageblit'
make[3]: *** [/tmp/next/build/scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1
make[2]: *** [/tmp/next/build/Makefile:1280: vmlinux] Error 2

Caused by commit

  c357150378862b (fbdev: au1100fb: Make driver compilable on non-mips platforms)

I have used the version from 20260205 instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-02-08 23:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-08 23:44 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-15  1:01 linux-next: build failure after merge of the fbdev tree Stephen Rothwell
2024-10-15  7:15 ` Thomas Zimmermann
2024-10-15  8:17   ` Helge Deller
2022-02-16  0:29 Stephen Rothwell
2022-02-16  7:16 ` Helge Deller
2019-06-20  1:41 Stephen Rothwell
2019-06-24  1:45 ` Stephen Rothwell
2019-06-24  4:15   ` Stephen Rothwell
2018-06-29  1:07 Stephen Rothwell
2018-06-29  9:32 ` Hans de Goede
2011-04-07  2:48 Stephen Rothwell

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=aYkfxvZGxTwUTQfK@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.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