From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
jani.nikula@intel.com, ville.syrjala@linux.intel.com,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH v2 0/7] drm: debug logging improvements
Date: Mon, 8 Apr 2024 12:23:55 +0300 [thread overview]
Message-ID: <cover.1712568037.git.jani.nikula@intel.com> (raw)
v2 of [1], dropping drm_mode_print() stuff altogether, and switching to
DRM_MODE_FMT/DRM_MODE_ARG() in a separate patch. Also add a few more drm
device based logging conversion patches, so the last patch makes more sense.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/130881/
Jani Nikula (7):
drm/probe-helper: switch to drm device based logging
drm/modes: switch to drm device based error logging
drm/sysfs: switch to drm device based logging
drm/client: switch to drm device based logging, and more
drm/crtc: switch to drm device based logging
drm/crtc-helper: switch to drm device based logging and warns
drm: prefer DRM_MODE_FMT/ARG over drm_mode_debug_printmodeline()
drivers/gpu/drm/drm_atomic_uapi.c | 6 +-
drivers/gpu/drm/drm_client_modeset.c | 129 +++++++++++++++------------
drivers/gpu/drm/drm_crtc.c | 38 ++++----
drivers/gpu/drm/drm_crtc_helper.c | 100 +++++++++++----------
drivers/gpu/drm/drm_modes.c | 40 ++++-----
drivers/gpu/drm/drm_probe_helper.c | 39 ++++----
drivers/gpu/drm/drm_sysfs.c | 20 ++---
7 files changed, 193 insertions(+), 179 deletions(-)
--
2.39.2
next reply other threads:[~2024-04-08 9:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:23 Jani Nikula [this message]
2024-04-08 9:23 ` [PATCH v2 1/7] drm/probe-helper: switch to drm device based logging Jani Nikula
2024-04-08 9:23 ` [PATCH v2 2/7] drm/modes: switch to drm device based error logging Jani Nikula
2024-04-08 9:23 ` [PATCH v2 3/7] drm/sysfs: switch to drm device based logging Jani Nikula
2024-04-08 9:23 ` [PATCH v2 4/7] drm/client: switch to drm device based logging, and more Jani Nikula
2024-04-08 9:24 ` [PATCH v2 5/7] drm/crtc: switch to drm device based logging Jani Nikula
2024-04-08 9:24 ` [PATCH v2 6/7] drm/crtc-helper: switch to drm device based logging and warns Jani Nikula
2024-04-08 12:38 ` Ville Syrjälä
2024-04-08 9:24 ` [PATCH v2 7/7] drm: prefer DRM_MODE_FMT/ARG over drm_mode_debug_printmodeline() Jani Nikula
2024-04-08 12:51 ` Ville Syrjälä
2024-04-08 11:15 ` [PATCH v2 0/7] drm: debug logging improvements Thomas Zimmermann
2024-04-08 18:39 ` ✗ Fi.CI.CHECKPATCH: warning for drm: debug logging improvements (rev2) Patchwork
2024-04-08 18:59 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-08 23:33 ` ✗ Fi.CI.CHECKPATCH: warning for drm: debug logging improvements (rev3) Patchwork
2024-04-08 23:33 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-08 23:44 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-09 14:44 ` ✗ Fi.CI.CHECKPATCH: warning for drm: debug logging improvements (rev4) Patchwork
2024-04-09 14:44 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-09 14:51 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-10 17:14 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-15 13:44 ` [PATCH v2 0/7] drm: debug logging improvements 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.1712568037.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).