Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: daniel@ffwll.ch, 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: Jim Cromie <jim.cromie@gmail.com>,
	David Airlie <airlied@gmail.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Maxime Ripard <mripard@kernel.org>
Subject: [Intel-gfx] [PATCH 0/5] drm_dbg: add trailing newlines where missing
Date: Sun, 30 Jul 2023 15:57:49 -0600	[thread overview]
Message-ID: <20230730215758.54010-1-jim.cromie@gmail.com> (raw)

Most of the (~1500) DRM.debug callsites provide a trailing newline in
their format-strings.  Fix the remainder to do the same.

no functional changes

Jim Cromie (5):
  drm_dbg: add trailing newlines to remaining callsites
  drm_dbg: add trailing newlines
  drm_dbg: add trailing newlines
  drm_dbg: add trailing newlines
  drm_dbg: add trailing newlines

 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 ++--
 7 files changed, 19 insertions(+), 17 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-07-30 21:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 21:57 Jim Cromie [this message]
2023-07-30 21:57 ` [Intel-gfx] [PATCH 1/5] drm_dbg: add trailing newlines to remaining callsites Jim Cromie
2023-07-30 21:57 ` [Intel-gfx] [PATCH 2/5] drm_dbg: add trailing newlines Jim Cromie
2023-07-30 21:57 ` [Intel-gfx] [PATCH 3/5] " Jim Cromie
2023-07-30 21:57 ` [Intel-gfx] [PATCH 4/5] " Jim Cromie
2023-07-30 21:57 ` [Intel-gfx] [PATCH 5/5] " Jim Cromie
2023-07-30 22:22 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm_dbg: add trailing newlines where missing Patchwork
2023-07-30 22:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-07-30 22:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-30 23:52 ` [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=20230730215758.54010-1-jim.cromie@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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