From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: linux-next: build failure after merge of the fbdev tree
Date: Mon, 24 Jun 2019 11:45:38 +1000 [thread overview]
Message-ID: <20190624114538.3531b28d@canb.auug.org.au> (raw)
In-Reply-To: <20190620114126.2f13ab9c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hi all,
On Thu, 20 Jun 2019 11:41:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the fbdev tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> x86_64-linux-gnu-ld: drivers/gpu/vga/vga_switcheroo.o: in function `vga_switchto_stage2':
> vga_switcheroo.c:(.text+0x997): undefined reference to `fbcon_remap_all'
>
> Caused by commit
>
> 1cd51b5d200d ("vgaswitcheroo: call fbcon_remap_all directly")
>
> I have used the version of the fbdev tree from next-20190619 for today.
I am still getting this failure.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-24 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 1:41 linux-next: build failure after merge of the fbdev tree Stephen Rothwell
2019-06-24 1:45 ` Stephen Rothwell [this message]
2019-06-24 4:15 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-02-16 0:29 Stephen Rothwell
2022-02-16 7:16 ` Helge Deller
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=20190624114538.3531b28d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).