From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/3] drm/i915: use drm->debugfs_root when creating debugfs files
Date: Wed, 11 Jun 2025 17:51:13 +0300 [thread overview]
Message-ID: <cover.1749653354.git.jani.nikula@intel.com> (raw)
In the long run, I think this will allow us to remove (or not add) some
drm_file.h includes. Currently the point is moot, because it will still
get implicitly included in most places. Regardless, this is the
direction anyway.
BR,
Jani.
Jani Nikula (3):
drm/i915/display: use drm->debugfs_root for creating debugfs files
drm/i915/gvt: use drm->debugfs_root for creating debugfs files
drm/i915: use drm->debugfs_root for creating debugfs files
drivers/gpu/drm/i915/display/intel_bios.c | 4 +---
drivers/gpu/drm/i915/display/intel_cdclk.c | 4 +---
.../drm/i915/display/intel_display_debugfs.c | 6 +++---
.../display/intel_display_debugfs_params.c | 6 +++---
drivers/gpu/drm/i915/display/intel_dmc.c | 4 +---
drivers/gpu/drm/i915/display/intel_dp_test.c | 3 +--
drivers/gpu/drm/i915/display/intel_fbc.c | 3 +--
drivers/gpu/drm/i915/display/intel_hotplug.c | 8 ++++----
drivers/gpu/drm/i915/display/intel_opregion.c | 4 +---
drivers/gpu/drm/i915/display/intel_psr.c | 6 +++---
drivers/gpu/drm/i915/display/intel_wm.c | 8 ++++----
drivers/gpu/drm/i915/display/skl_watermark.c | 6 +++---
drivers/gpu/drm/i915/gt/intel_gt_debugfs.c | 5 +++--
drivers/gpu/drm/i915/gvt/debugfs.c | 12 +++++------
drivers/gpu/drm/i915/i915_debugfs.c | 20 +++++++++----------
drivers/gpu/drm/i915/i915_debugfs_params.c | 4 ++--
drivers/gpu/drm/i915/i915_gpu_error.c | 6 +++---
drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c | 8 ++++----
18 files changed, 53 insertions(+), 64 deletions(-)
--
2.39.5
next reply other threads:[~2025-06-11 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 14:51 Jani Nikula [this message]
2025-06-11 14:51 ` [PATCH 1/3] drm/i915/display: use drm->debugfs_root for creating debugfs files Jani Nikula
2025-06-11 14:51 ` [PATCH 2/3] drm/i915/gvt: " Jani Nikula
2025-06-11 14:51 ` [PATCH 3/3] drm/i915: " Jani Nikula
2025-06-11 15:41 ` ✗ CI.checkpatch: warning for drm/i915: use drm->debugfs_root when " Patchwork
2025-06-11 15:43 ` ✓ CI.KUnit: success " Patchwork
2025-06-11 15:58 ` ✓ CI.Build: " Patchwork
2025-06-11 16:01 ` ✓ CI.Hooks: " Patchwork
2025-06-11 16:03 ` ✗ CI.checksparse: warning " Patchwork
2025-06-11 16:52 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-11 17:03 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-06-11 17:31 ` ✓ i915.CI.BAT: success " Patchwork
2025-06-11 19:30 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-11 20:38 ` ✓ i915.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=cover.1749653354.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 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.