From: Brahmajit Das <listout@listout•xyz>
To: jani.nikula@linux•intel.com
Cc: dri-devel@lists•freedesktop.org, intel-gfx@lists•freedesktop.org,
intel-xe@lists•freedesktop.org, joonas.lahtinen@linux•intel.com,
linux-next@vger•kernel.org, listout@listout•xyz,
rodrigo.vivi@intel•com, simona@ffwll•ch, tursulin@ursulin•net
Subject: [RFC PATCH 0/2] use new debugfs device-centered functions
Date: Mon, 11 Aug 2025 18:41:24 +0530 [thread overview]
Message-ID: <20250811131126.71883-1-listout@listout.xyz> (raw)
In-Reply-To: <32c55ab0b1452a1fd8ef49e8a1ca640ad5bd9d76@intel.com>
Replace the use of drm_debugfs_create_files() with the new
drm_debugfs_add_files() function, which centers the debugfs files
management on the drm_device.
Refer:
https://docs.kernel.org/gpu/todo.html#clean-up-the-debugfs-support
Brahmajit Das (2):
drm/i915/debugfs: use new debugfs device-centered functions
drm/i915: use new debugfs device-centered functions
drivers/gpu/drm/i915/display/intel_display_debugfs.c | 7 +++----
drivers/gpu/drm/i915/i915_debugfs.c | 7 +++----
2 files changed, 6 insertions(+), 8 deletions(-)
--
2.50.1
next prev parent reply other threads:[~2025-08-11 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 22:52 [RFC PATCH 0/2] use new debugfs device-centered functions Brahmajit Das
2025-08-08 22:52 ` [RFC PATCH 1/2] drm/i915/debugfs: " Brahmajit Das
2025-08-08 22:52 ` [RFC PATCH 2/2] drm/i915: " Brahmajit Das
2025-08-11 10:23 ` [RFC PATCH 0/2] " Jani Nikula
2025-08-11 13:11 ` Brahmajit Das [this message]
2025-08-11 13:11 ` [RFC PATCH 1/2] drm/i915/debugfs: " Brahmajit Das
2025-08-11 13:11 ` [RFC PATCH 2/2] drm/i915: " Brahmajit Das
2025-08-11 13:17 ` [RFC PATCH 0/2] " Brahmajit Das
2025-08-11 13:17 ` [RFC PATCH v2 1/2] drm/i915/debugfs: " Brahmajit Das
2025-08-11 13:17 ` [RFC PATCH v2 2/2] drm/i915: " Brahmajit Das
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=20250811131126.71883-1-listout@listout.xyz \
--to=listout@listout$(echo .)xyz \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=intel-xe@lists$(echo .)freedesktop.org \
--cc=jani.nikula@linux$(echo .)intel.com \
--cc=joonas.lahtinen@linux$(echo .)intel.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rodrigo.vivi@intel$(echo .)com \
--cc=simona@ffwll$(echo .)ch \
--cc=tursulin@ursulin$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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