From: Sean Paul <seanpaul@chromium.org>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/3] Fix compile/link errors
Date: Mon, 6 Mar 2017 15:27:12 -0500 [thread overview]
Message-ID: <20170306202722.9301-1-seanpaul@chromium.org> (raw)
This set fixes 3 compile/linker errors when certain CONFIG options are not defined.
Sean Paul (3):
drm: Fix compilation error when CONFIG_DEBUG_FS is undefined
drm/rockchip: Fix link error when CONFIG_DRM_ANALOGIX_DP undefined
drm/msm: Fix compilation error when CONFIG_DEBUG_FS undefined
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 2 ++
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 10 ++++++++++
include/drm/drm_crtc.h | 2 +-
3 files changed, 13 insertions(+), 1 deletion(-)
--
2.12.0.rc1.440.g5b76565f74-goog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-03-06 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 20:27 Sean Paul [this message]
2017-03-06 20:27 ` [PATCH 1/3] drm: Fix compilation error when CONFIG_DEBUG_FS is undefined Sean Paul
2017-03-06 23:43 ` Sean Paul
2017-03-06 20:27 ` [PATCH 2/3] drm/rockchip: Fix link error when CONFIG_DRM_ANALOGIX_DP undefined Sean Paul
2017-03-06 20:58 ` Emil Velikov
2017-03-06 23:15 ` Sean Paul
2017-03-06 23:44 ` Sean Paul
[not found] ` <20170306202722.9301-1-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-06 20:27 ` [PATCH 3/3] drm/msm: Fix compilation error when CONFIG_DEBUG_FS undefined Sean Paul
2017-03-06 20:35 ` [Freedreno] " Jordan Crouse
[not found] ` <20170306203537.GA20962-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2017-03-06 23:43 ` Sean Paul
[not found] ` <20170306202722.9301-4-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-06 20:51 ` Emil Velikov
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=20170306202722.9301-1-seanpaul@chromium.org \
--to=seanpaul@chromium.org \
--cc=dri-devel@lists.freedesktop.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).