From: "Michał Grzelak" <michal.grzelak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/xe/display: clean up xe_initial_plane.c includes
Date: Mon, 2 Mar 2026 21:07:33 +0100 (CET) [thread overview]
Message-ID: <ba0ec5b3-03ce-a6ff-4492-07aff9ca030c@intel.com> (raw)
In-Reply-To: <637eab7df00a540df6b7ca1ca345302864b6342f.1772212579.git.jani.nikula@intel.com>
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
On Fri, 27 Feb 2026, Jani Nikula wrote:
> Remove excess includes, group and sort include directives.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>
BR,
Michał
next prev parent reply other threads:[~2026-03-02 20:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 17:17 [PATCH 0/4] drm/i915, drm/xe: clean up i915_vma.h usage for display Jani Nikula
2026-02-27 17:17 ` [PATCH 1/4] drm/i915/fbdev: stop debug logging i915_ggtt_offset() Jani Nikula
2026-03-02 20:06 ` Michał Grzelak
2026-03-03 14:16 ` Jani Nikula
2026-02-27 17:17 ` [PATCH 2/4] drm/i915: add VMA to parent interface Jani Nikula
2026-03-02 20:07 ` Michał Grzelak
2026-03-03 16:11 ` Ville Syrjälä
2026-03-04 10:55 ` Jani Nikula
2026-02-27 17:17 ` [PATCH 3/4] drm/xe/compat: remove i915_vma.h from compat Jani Nikula
2026-03-02 20:07 ` Michał Grzelak
2026-02-27 17:17 ` [PATCH 4/4] drm/xe/display: clean up xe_initial_plane.c includes Jani Nikula
2026-03-02 20:07 ` Michał Grzelak [this message]
2026-02-27 19:23 ` ✗ CI.checkpatch: warning for drm/i915, drm/xe: clean up i915_vma.h usage for display Patchwork
2026-02-27 19:24 ` ✓ CI.KUnit: success " Patchwork
2026-02-27 19:40 ` ✓ i915.CI.BAT: " Patchwork
2026-02-27 20:43 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-28 1:10 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-28 9:31 ` ✓ Xe.CI.FULL: success " 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=ba0ec5b3-03ce-a6ff-4492-07aff9ca030c@intel.com \
--to=michal.grzelak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 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.