Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for drm/i915: move i915 specific display adaptation files to display-adapt
Date: Thu, 16 Oct 2025 01:05:08 -0000	[thread overview]
Message-ID: <176057670837.20008.9513515647633570491@97596180aaec> (raw)
In-Reply-To: <20251015160140.2296120-1-jani.nikula@intel.com>

== Series Details ==

Series: drm/i915: move i915 specific display adaptation files to display-adapt
URL   : https://patchwork.freedesktop.org/series/156006/
State : warning

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
fbd08a78c3a3bb17964db2a326514c69c1dca660
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 4ccae0b077da7deed4f0a7d26600eefa62594009
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Wed Oct 15 19:01:40 2025 +0300

    drm/i915: move i915 specific display adaptation files to display-adapt
    
    The display/ subdirectory currently contains files that are about i915
    core driver adaptation to display rather than generic display
    implementation. Move them to a new i915 subdirectory display-adapt/.
    
    In the xe driver, all of its display/ is basically xe core adaptation to
    display. It's just that i915 display/ contains the actual display
    implementation for both. Ideally, we'd have the shared display code
    somewhere else, and the adaptation in i915 would be under display/, but
    we're not quite ready for that kind of churn yet. So let's just call it
    display-adapt for now.
    
    xe basically has equivalent files to the ones that are being moved,
    apart from intel_dpt.c, for which the implementation is quite different.
    
    Cc: Lucas De Marchi <lucas.demarchi@intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Signed-off-by: Jani Nikula <jani.nikula@intel.com>
+ /mt/dim checkpatch f019aaad58112f89234f7b68557c831846437008 drm-intel
4ccae0b077da drm/i915: move i915 specific display adaptation files to display-adapt
-:115: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#115: 
rename from drivers/gpu/drm/i915/display/intel_bo.c

total: 0 errors, 1 warnings, 0 checks, 238 lines checked



  reply	other threads:[~2025-10-16  1:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 16:01 [RFC] drm/i915: move i915 specific display adaptation files to display-adapt Jani Nikula
2025-10-16  1:05 ` Patchwork [this message]
2025-10-16  1:06 ` ✓ CI.KUnit: success for " Patchwork
2025-10-16  1:45 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-16 19:04 ` ✓ Xe.CI.Full: " Patchwork
2025-10-16 19:42 ` [RFC] " Rodrigo Vivi
2025-10-21  9:00   ` Jani Nikula
2025-10-21 15:03     ` Rodrigo Vivi
2025-11-25 14:01 ` Jani Nikula
2025-11-25 17:30   ` Ville Syrjälä

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=176057670837.20008.9513515647633570491@97596180aaec \
    --to=patchwork@emeril.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox