From: Sven Joachim <svenjoac@gmx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Dave Airlie <airlied@redhat.com>
Subject: Linux 5.1.9 build failure with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n
Date: Tue, 11 Jun 2019 15:56:35 +0200 [thread overview]
Message-ID: <87k1dsjkdo.fsf@turtle.gmx.de> (raw)
Commit 1e07d63749 ("drm/nouveau: add kconfig option to turn off nouveau
legacy contexts. (v3)") has caused a build failure for me when I
actually tried that option (CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n):
,----
| Kernel: arch/x86/boot/bzImage is ready (#1)
| Building modules, stage 2.
| MODPOST 290 modules
| ERROR: "drm_legacy_mmap" [drivers/gpu/drm/nouveau/nouveau.ko] undefined!
| scripts/Makefile.modpost:91: recipe for target '__modpost' failed
`----
Upstream does not have that problem, as commit bed2dd8421 ("drm/ttm:
Quick-test mmap offset in ttm_bo_mmap()") has removed the use of
drm_legacy_mmap from nouveau_ttm.c. Unfortunately that commit does not
apply in 5.1.9.
Most likely 4.19.50 and 4.14.125 are also affected, I haven't tested
them yet.
Cheers,
Sven
next reply other threads:[~2019-06-11 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 13:56 Sven Joachim [this message]
2019-06-11 15:36 ` Linux 5.1.9 build failure with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n Greg Kroah-Hartman
2019-06-11 17:33 ` Daniel Vetter
2019-06-11 17:40 ` Greg Kroah-Hartman
2019-06-11 19:08 ` Thomas Backlund
2019-06-11 19:42 ` Daniel Vetter
2019-06-11 19:43 ` Sven Joachim
2019-06-11 19:58 ` Thomas Backlund
2019-06-11 19:39 ` Daniel Vetter
2019-06-13 7:42 ` Greg Kroah-Hartman
2019-06-15 10:21 ` Thomas Backlund
2019-06-15 15:27 ` Greg Kroah-Hartman
2019-06-11 18:53 ` Sven Joachim
2019-06-11 19:41 ` Daniel Vetter
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=87k1dsjkdo.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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).