From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: dim-tools@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PULL] topic/drmp-cleanup for drm-misc-next and drm-intel-next-queued
Date: Mon, 7 Jan 2019 19:10:27 +0100 [thread overview]
Message-ID: <20190107181027.u76v4lmr5kdql26u@flea> (raw)
In-Reply-To: <87pntfl6pa.fsf@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]
Hi Jani,
On Wed, Jan 02, 2019 at 12:00:49PM +0200, Jani Nikula wrote:
> 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.
I merged the PR, and it's on its way to Daniel and Dave now.
Thanks
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-01-07 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:00 [PULL] topic/drmp-cleanup for drm-misc-next and drm-intel-next-queued Jani Nikula
2019-01-07 18:10 ` Maxime Ripard [this message]
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=20190107181027.u76v4lmr5kdql26u@flea \
--to=maxime.ripard@bootlin.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=jani.nikula@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=rodrigo.vivi@intel.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