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>,
Hans de Goede <hdegoede@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: linux-next: build failure after merge of the fbdev tree
Date: Fri, 29 Jun 2018 11:07:44 +1000 [thread overview]
Message-ID: <20180629110744.29b54355@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hi Bartlomiej,
After merging the fbdev tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "dummycon_unregister_output_notifier" [drivers/video/fbdev/core/fb.ko] undefined!
ERROR: "dummycon_register_output_notifier" [drivers/video/fbdev/core/fb.ko] undefined!
Caused by commit
83d83bebf401 ("console/fbcon: Add support for deferred console takeover")
I have reverted that commit for today.
I note that this commit is in the drm-misc tree as well.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-06-29 1:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 1:07 Stephen Rothwell [this message]
2018-06-29 9:32 ` linux-next: build failure after merge of the fbdev tree Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
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
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=20180629110744.29b54355@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--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).