From: Jim Cromie <jim.cromie@gmail.com>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, daniel.vetter@ffwll.ch,
Jim Cromie <jim.cromie@gmail.com>,
seanpaul@chromium.org, daniel@ffwll.ch
Subject: [Intel-gfx] [PATCH v2 0/6] drm_dbg: add trailing newlines where missing
Date: Sun, 3 Sep 2023 12:45:57 -0600 [thread overview]
Message-ID: <20230903184607.272198-1-jim.cromie@gmail.com> (raw)
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.
V1 got Fi.CI.IGT failure, on 2 Possible regressions:
igt@api_intel_bb@render@render-y-1024:
shard-snb: NOTRUN -> ABORT +1 similar issue
igt@sysfs_timeslice_duration@timeout@ccs0:
shard-dg2: PASS -> TIMEOUT
Neither have any logs bearing anything connected with drm.debug output.
V2 tries again.
and fixes checkpatch warnings, by reusing 1st commit-msg.
also fix a ccflags-y spelling error in drm Makefile.
commits upon
e2884fe84a83 (drm-misc/for-linux-next-fixes, drm-misc/drm-misc-fixes) drm/amd: \
Make fence wait in suballocator uninterruptible
Jim Cromie (6):
drm_dbg: add trailing newlines to msgs
drm_dbg: add trailing newlines to msgs
drm_dbg: add trailing newlines to msgs
drm_dbg: add trailing newlines to msgs
drm_dbg: add trailing newlines to msgs
drm: use correct ccflags-y syntax
drivers/gpu/drm/Makefile | 3 ++-
drivers/gpu/drm/drm_connector.c | 4 +++-
drivers/gpu/drm/i915/display/intel_ddi.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.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 | 6 +++---
drivers/gpu/drm/vc4/vc4_crtc.c | 4 ++--
8 files changed, 21 insertions(+), 18 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-03 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 18:45 Jim Cromie [this message]
2023-09-03 18:45 ` [Intel-gfx] [PATCH v2 1/6] drm_dbg: add trailing newlines to msgs Jim Cromie
2023-09-03 18:45 ` [Intel-gfx] [PATCH v2 2/6] " Jim Cromie
2023-09-03 18:46 ` [Intel-gfx] [PATCH v2 3/6] " Jim Cromie
2023-09-04 6:32 ` Andi Shyti
2023-09-06 16:42 ` Rodrigo Vivi
2023-09-06 18:06 ` jim.cromie
2023-09-03 18:46 ` [Intel-gfx] [PATCH v2 4/6] " Jim Cromie
2023-09-03 18:46 ` [Intel-gfx] [PATCH v2 5/6] " Jim Cromie
2023-09-03 18:46 ` [Intel-gfx] [PATCH v2 6/6] drm: use correct ccflags-y syntax Jim Cromie
2023-09-03 19:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm_dbg: add trailing newlines where missing (rev2) Patchwork
2023-09-03 19:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-03 19:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-03 20:48 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230903184607.272198-1-jim.cromie@gmail.com \
--to=jim.cromie@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.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