From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 5/5] drm/i915: split out gem/i915_gem_domain.h from i915_drv.h
Date: Tue, 25 Jan 2022 17:25:15 +0200 [thread overview]
Message-ID: <87wninzvl0.fsf@intel.com> (raw)
In-Reply-To: <8328facd-f10d-01e6-12e8-67179fbf324e@linux.intel.com>
On Mon, 24 Jan 2022, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> All looks sane.
>
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Thanks... but I didn't realize this already conflicts between
drm-intel-next and drm-intel-gt-next. I wonder what the best plan would
be for making this happen.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-25 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 8:51 [Intel-gfx] [PATCH 0/5] drm/i915: clean up i915_drv.h, part 2, take 2 Jani Nikula
2022-01-12 8:51 ` [Intel-gfx] [PATCH 1/5] drm/i915: split out i915_gem_internal.h from i915_drv.h Jani Nikula
2022-01-12 8:51 ` [Intel-gfx] [PATCH 2/5] drm/i915: remove leftover i915_gem_pm.h declarations " Jani Nikula
2022-01-12 8:51 ` [Intel-gfx] [PATCH 3/5] drm/i915: split out gem/i915_gem_dmabuf.h " Jani Nikula
2022-01-12 8:51 ` [Intel-gfx] [PATCH 4/5] drm/i915: split out gem/i915_gem_create.h " Jani Nikula
2022-01-12 8:51 ` [Intel-gfx] [PATCH 5/5] drm/i915: split out gem/i915_gem_domain.h " Jani Nikula
2022-01-24 12:19 ` Maarten Lankhorst
2022-01-25 15:25 ` Jani Nikula [this message]
2022-01-26 7:22 ` Maarten Lankhorst
2022-01-12 9:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: clean up i915_drv.h, part 2, take 2 Patchwork
2022-01-12 9:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-12 9:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-12 11:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=87wninzvl0.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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