From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [RESEND 0/5] drm/i915/plane: file and function renames
Date: Tue, 17 Jun 2025 11:13:35 +0300 [thread overview]
Message-ID: <cover.1750147992.git.jani.nikula@intel.com> (raw)
Jani Nikula (5):
drm/i915/plane: rename intel_atomic_plane.[ch] to intel_plane.[ch]
drm/i915/plane: drop atomic from intel_atomic_plane_check_clipping()
drm/i915/plane: make intel_plane_atomic_check() static and rename
drm/i915/plane: rename intel_atomic_check_planes() to
intel_plane_atomic_check()
drm/i915/plane: rename intel_atomic_add_affected_planes() to
intel_plane_add_affected()
Documentation/gpu/i915.rst | 4 ++--
drivers/gpu/drm/i915/Makefile | 4 ++--
drivers/gpu/drm/i915/display/i9xx_plane.c | 10 ++++-----
drivers/gpu/drm/i915/display/intel_atomic.c | 2 +-
drivers/gpu/drm/i915/display/intel_cdclk.c | 2 +-
drivers/gpu/drm/i915/display/intel_crtc.c | 2 +-
drivers/gpu/drm/i915/display/intel_cursor.c | 10 ++++-----
drivers/gpu/drm/i915/display/intel_display.c | 8 +++----
.../gpu/drm/i915/display/intel_display_irq.c | 2 +-
drivers/gpu/drm/i915/display/intel_fb.c | 2 +-
drivers/gpu/drm/i915/display/intel_fb_pin.c | 2 +-
.../{intel_atomic_plane.c => intel_plane.c} | 22 +++++++++----------
.../{intel_atomic_plane.h => intel_plane.h} | 22 +++++++++----------
.../drm/i915/display/intel_plane_initial.c | 2 +-
drivers/gpu/drm/i915/display/intel_sprite.c | 14 ++++++------
.../drm/i915/display/skl_universal_plane.c | 7 +++---
drivers/gpu/drm/i915/display/skl_watermark.c | 2 +-
drivers/gpu/drm/xe/Makefile | 2 +-
drivers/gpu/drm/xe/display/xe_plane_initial.c | 2 +-
19 files changed, 59 insertions(+), 62 deletions(-)
rename drivers/gpu/drm/i915/display/{intel_atomic_plane.c => intel_plane.c} (98%)
rename drivers/gpu/drm/i915/display/{intel_atomic_plane.h => intel_plane.h} (86%)
--
2.39.5
next reply other threads:[~2025-06-17 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 8:13 Jani Nikula [this message]
2025-06-17 8:13 ` [RESEND 1/5] drm/i915/plane: rename intel_atomic_plane.[ch] to intel_plane.[ch] Jani Nikula
2025-06-17 8:13 ` [RESEND 2/5] drm/i915/plane: drop atomic from intel_atomic_plane_check_clipping() Jani Nikula
2025-06-17 8:13 ` [RESEND 3/5] drm/i915/plane: make intel_plane_atomic_check() static and rename Jani Nikula
2025-06-17 8:13 ` [RESEND 4/5] drm/i915/plane: rename intel_atomic_check_planes() to intel_plane_atomic_check() Jani Nikula
2025-06-17 8:13 ` [RESEND 5/5] drm/i915/plane: rename intel_atomic_add_affected_planes() to intel_plane_add_affected() Jani Nikula
2025-06-17 15:20 ` ✗ i915.CI.BAT: failure for drm/i915/plane: file and function renames (rev6) Patchwork
2025-06-17 19:41 ` Jani Nikula
2025-06-18 6:39 ` Ravali, JupallyX
2025-06-18 6:34 ` ✓ i915.CI.BAT: success " Patchwork
2025-06-18 21:02 ` ✓ i915.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-06-12 11:37 [RESEND 0/5] drm/i915/plane: file and function renames Jani Nikula
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=cover.1750147992.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).