From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: build failure after merge of the fbdev tree
Date: Fri, 29 Jun 2018 11:32:08 +0200 [thread overview]
Message-ID: <dff81030-46bd-b80b-3d66-8ccb925accc8@redhat.com> (raw)
In-Reply-To: <20180629110744.29b54355@canb.auug.org.au>
Hi,
On 29-06-18 03:07, Stephen Rothwell wrote:
> 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.
Ugh, my bad. I did not take the fb code being modular into account
here. I will submit a follow up patch fixing this today.
Regards,
Hans
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-29 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 1:07 linux-next: build failure after merge of the fbdev tree Stephen Rothwell
2018-06-29 9:32 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-08 23:44 Mark Brown
2024-10-15 1:01 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
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=dff81030-46bd-b80b-3d66-8ccb925accc8@redhat.com \
--to=hdegoede@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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