[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230906190224.583577-1-jim.cromie@gmail.com>
Date: Wed, 6 Sep 2023 13:02:18 -0600
From: Jim Cromie <jim.cromie@...il.com>
To: linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
amd-gfx@...ts.freedesktop.org, intel-gvt-dev@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org
Cc: daniel.vetter@...ll.ch, daniel@...ll.ch, jani.nikula@...el.com,
ville.syrjala@...ux.intel.com, seanpaul@...omium.org,
robdclark@...il.com, Jim Cromie <jim.cromie@...il.com>
Subject: [PATCH v3 0/5] drm/drm_dbg: add trailing newlines where missing
By at least strong convention, a print-buffer's trailing newline says
"message complete, send it". The exception (no TNL, followed by a call
to pr_cont) proves the general rule.
Most DRM.debug calls already comport with this rule/convention:
207 DRM_DEV_DEBUG, 1288 drm_dbg. Clean up the remainders, in
maintainer sized chunks.
V3: adds proper "drm/<component>:" to subject, as suggested by Rodrigo.
drops drm/i915: already applied by Rodrigo.
Jim Cromie (5):
drm/connector: add trailing newlines to drm_dbg msgs
drm/kmb: add trailing newlines to drm_dbg msgs
drm/msm: add trailing newlines to drm_dbg msgs
drm/vc4: add trailing newlines to drm_dbg msgs
drm/Makefile: use correct ccflags-y syntax
drivers/gpu/drm/Makefile | 3 ++-
drivers/gpu/drm/drm_connector.c | 4 +++-
drivers/gpu/drm/kmb/kmb_crtc.c | 10 +++++-----
drivers/gpu/drm/kmb/kmb_plane.c | 6 +++---
drivers/gpu/drm/msm/msm_fb.c | 10 +++++-----
drivers/gpu/drm/vc4/vc4_crtc.c | 4 ++--
6 files changed, 20 insertions(+), 17 deletions(-)
--
2.41.0
Powered by blists - more mailing lists