From: Qian Cai <cai@lca.pw>
To: airlied@linux.ie, daniel@ffwll.ch
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
sean@poorly.run, yamada.masahiro@socionext.com,
michal.lkml@markovi.net, emil.l.velikov@gmail.com,
dri-devel@lists.freedesktop.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, Qian Cai <cai@lca.pw>
Subject: [RFC PATCH] gpu: no need to compile drm/ if CONFIG_DRM=n
Date: Wed, 11 Sep 2019 13:34:53 -0400 [thread overview]
Message-ID: <20190911173453.958-1-cai@lca.pw> (raw)
The commit c0e09200dc08 ("drm: reorganise drm tree to be more future
proof.") changed the behavior from only compiling drm/ if CONFIG_DRM=y
to always compiling drm/. This restores the behavior, so people don't
need to waste time compiling stuff they don't need.
Fixes: c0e09200dc08 ("drm: reorganise drm tree to be more future proof.")
---
drivers/gpu/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/Makefile b/drivers/gpu/Makefile
index f17d01f076c7..a793b9ace34b 100644
--- a/drivers/gpu/Makefile
+++ b/drivers/gpu/Makefile
@@ -3,5 +3,6 @@
# taken to initialize them in the correct order. Link order is the only way
# to ensure this currently.
obj-$(CONFIG_TEGRA_HOST1X) += host1x/
-obj-y += drm/ vga/
+obj-$(CONFIG_DRM) += drm/
+obj-y += vga/
obj-$(CONFIG_IMX_IPUV3_CORE) += ipu-v3/
--
2.20.1 (Apple Git-117)
next reply other threads:[~2019-09-11 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:34 Qian Cai [this message]
[not found] ` <CAO4ZVTMUMKMOqef5yV=5bwHLXLMsNtTegGGMkw0GbFaDHvrV6g@mail.gmail.com>
2019-09-11 17:41 ` [RFC PATCH] gpu: no need to compile drm/ if CONFIG_DRM=n Qian Cai
2019-09-12 0:52 ` Masahiro Yamada
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=20190911173453.958-1-cai@lca.pw \
--to=cai@lca.pw \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.lkml@markovi.net \
--cc=mripard@kernel.org \
--cc=sean@poorly.run \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).