From: Thomas Huth <thuth@redhat.com>
To: Gustavo Padovan <gustavo@padovan.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, Gerd Hoffmann <kraxel@redhat.com>,
Farhan Ali <alifm@linux.ibm.com>,
borntraeger@de.ibm.com
Subject: [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C
Date: Fri, 13 Apr 2018 11:40:54 +0200 [thread overview]
Message-ID: <1523612456-14827-1-git-send-email-thuth@redhat.com> (raw)
By enabling the DRM code for virtio-gpu on S390, you currently also get
all the code that is enabled by CONFIG_HDMI and CONFIG_I2C automatically.
This is quite ugly, since on S390, there is no HDMI and no I2C. Thus it
would be great if the DRM code could also be compiled without CONFIG_HDMI
and CONFIG_I2C. These two patches now refactor the DRM code a little bit
so that we can compile it also without CONFIG_HDMI and CONFIG_I2C.
Thomas Huth (2):
drivers/gpu/drm: Move CONFIG_HDMI-dependent code to a separate file
drivers/gpu/drm: Make the DRM code compilable without CONFIG_I2C
drivers/gpu/drm/Kconfig | 6 +-
drivers/gpu/drm/Makefile | 17 ++--
drivers/gpu/drm/drm_crtc_internal.h | 2 +
drivers/gpu/drm/drm_edid.c | 173 ++--------------------------------
drivers/gpu/drm/drm_hdmi.c | 182 ++++++++++++++++++++++++++++++++++++
5 files changed, 206 insertions(+), 174 deletions(-)
create mode 100644 drivers/gpu/drm/drm_hdmi.c
--
1.8.3.1
next reply other threads:[~2018-04-13 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 9:40 Thomas Huth [this message]
2018-04-13 9:40 ` [PATCH 1/2] drm: Move CONFIG_HDMI-dependent code to a separate file Thomas Huth
2018-04-13 9:40 ` [PATCH 2/2] drm: Make the DRM code compilable without CONFIG_I2C Thomas Huth
2018-04-13 13:04 ` Jani Nikula
2018-04-13 14:32 ` [PATCH 0/2] drm: Make it compilable without CONFIG_HDMI and CONFIG_I2C Daniel Vetter
2018-04-13 14:46 ` Thomas Huth
2018-04-13 14:53 ` 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=1523612456-14827-1-git-send-email-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=airlied@linux.ie \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=seanpaul@chromium.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
Powered by JetHome