From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/8] drm: drm debug and error logging improvements
Date: Fri, 24 Nov 2023 14:43:54 +0200 [thread overview]
Message-ID: <cover.1700829750.git.jani.nikula@intel.com> (raw)
Make drm_err_printer() drm device specific, and add drm device specific
drm_dbg_printer(). Switch code over to use them.
Jani Nikula (8):
drm/print: make drm_err_printer() device specific by using drm_err()
drm/print: move enum drm_debug_category etc. earlier in drm_print.h
drm/print: add drm_dbg_printer() for drm device specific printer
drm/dp_mst: switch from drm_debug_printer() to device specific
drm_dbg_printer()
drm/mode: switch from drm_debug_printer() to device specific
drm_dbg_printer()
drm/dp: switch drm_dp_vsc_sdp_log() to struct drm_printer
drm/i915: switch from drm_debug_printer() to device specific
drm_dbg_printer()
drm/i915: use drm_printf() with the drm_err_printer intead of pr_err()
drivers/gpu/drm/display/drm_dp_helper.c | 17 +-
drivers/gpu/drm/display/drm_dp_mst_topology.c | 23 +-
drivers/gpu/drm/drm_mode_config.c | 2 +-
drivers/gpu/drm/drm_print.c | 28 ++-
.../drm/i915/display/intel_crtc_state_dump.c | 5 +-
drivers/gpu/drm/i915/display/intel_display.c | 27 ++-
.../drm/i915/display/intel_display_driver.c | 3 +-
.../gpu/drm/i915/gt/intel_engine_heartbeat.c | 3 +-
drivers/gpu/drm/i915/gt/intel_reset.c | 3 +-
drivers/gpu/drm/i915/gt/intel_workarounds.c | 3 +-
drivers/gpu/drm/i915/gt/selftest_context.c | 3 +-
.../drm/i915/gt/selftest_engine_heartbeat.c | 10 +-
drivers/gpu/drm/i915/i915_driver.c | 3 +-
drivers/gpu/drm/i915/selftests/i915_active.c | 8 +-
include/drm/display/drm_dp_helper.h | 3 +-
include/drm/drm_print.h | 217 ++++++++++--------
16 files changed, 209 insertions(+), 149 deletions(-)
--
2.39.2
next reply other threads:[~2023-11-24 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 12:43 Jani Nikula [this message]
2023-11-24 12:43 ` [Intel-gfx] [PATCH 1/8] drm/print: make drm_err_printer() device specific by using drm_err() Jani Nikula
2023-11-24 12:43 ` [Intel-gfx] [PATCH 2/8] drm/print: move enum drm_debug_category etc. earlier in drm_print.h Jani Nikula
2023-11-24 12:43 ` [Intel-gfx] [PATCH 3/8] drm/print: add drm_dbg_printer() for drm device specific printer Jani Nikula
2023-11-24 12:43 ` [Intel-gfx] [PATCH 4/8] drm/dp_mst: switch from drm_debug_printer() to device specific drm_dbg_printer() Jani Nikula
2023-11-24 12:43 ` [Intel-gfx] [PATCH 5/8] drm/mode: " Jani Nikula
2023-11-24 12:44 ` [Intel-gfx] [PATCH 6/8] drm/dp: switch drm_dp_vsc_sdp_log() to struct drm_printer Jani Nikula
2023-11-24 12:44 ` [Intel-gfx] [PATCH 7/8] drm/i915: switch from drm_debug_printer() to device specific drm_dbg_printer() Jani Nikula
2023-11-24 12:44 ` [Intel-gfx] [PATCH 8/8] drm/i915: use drm_printf() with the drm_err_printer intead of pr_err() Jani Nikula
2023-11-24 17:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: drm debug and error logging improvements Patchwork
2023-11-24 17:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-24 17:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-26 3:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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.1700829750.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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