From: Jani Nikula <jani.nikula@intel.com>
To: Sean Paul <sean@poorly.run>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>
Cc: dim-tools@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [PULL] topic/drmp-cleanup for drm-misc-next and drm-intel-next-queued
Date: Wed, 02 Jan 2019 12:00:49 +0200 [thread overview]
Message-ID: <87pntfl6pa.fsf@intel.com> (raw)
Hi Sean, Maarten & Maxime -
I embarked on removing drmP.h includes from i915, but that requires a
bunch of drm header cleanup to add relevant includes and forward
declarations. Due to the timing, propagating the patches back to i915
would take eons, so Daniel suggested a topic branch to be merged both to
drm-misc-next and drm-intel-next-queued. So here it is, with $(git
merge-base drm-misc-next drm-intel-next-queued) as the starting point.
The topic branch has been part of drm-tip since, uh, last year, but I
did just force push it to update the commit messages to reflect
Laurent's review. No code changes.
I'll merge the same thing to i915 after it's been pulled to
drm-misc-next, and with this, I should be able to get rid of all drmP.h
includes in i915.
BR,
Jani.
The following changes since commit b4bf44d2dcbd6c35d9651bc6286e4940b8b3df95:
drm/i915: Update DRIVER_DATE to 20181122 (2018-11-22 16:49:47 +0200)
are available in the git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/topic/drmp-cleanup-2019-01-02
for you to fetch changes up to dd7ece7f6e220e4d1a2a8ba4c42622d7d73e6376:
drm: forward declare struct drm_file in drm_syncobj.h (2019-01-02 11:38:08 +0200)
----------------------------------------------------------------
Make some drm headers self-contained with includes and forward declarations
----------------------------------------------------------------
Jani Nikula (5):
drm: un-inline drm_legacy_findmap()
drm: include kernel.h and agp_backend.h from intel-gtt.h
drm: include idr.h from drm_file.h
drm: include types.h from drm_hdcp.h
drm: forward declare struct drm_file in drm_syncobj.h
drivers/gpu/drm/drm_bufs.c | 11 +++++++++++
include/drm/drm_file.h | 1 +
include/drm/drm_hdcp.h | 2 ++
include/drm/drm_legacy.h | 14 ++++----------
include/drm/drm_syncobj.h | 4 +++-
include/drm/intel-gtt.h | 3 +++
6 files changed, 24 insertions(+), 11 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-01-02 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:00 Jani Nikula [this message]
2019-01-07 18:10 ` [PULL] topic/drmp-cleanup for drm-misc-next and drm-intel-next-queued Maxime Ripard
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=87pntfl6pa.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.