From: Stephen Boyd <swboyd@chromium.org> To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com> Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev, dri-devel@lists.freedesktop.org, Simon Ser <contact@emersion.fr>, Pekka Paalanen <pekka.paalanen@collabora.com>, Daniel Vetter <daniel.vetter@ffwll.ch> Subject: [PATCH] drm/connector: Add newline to debug printk Date: Fri, 25 Aug 2023 16:31:17 -0700 [thread overview] Message-ID: <20230825233118.2689222-1-swboyd@chromium.org> (raw) This debug printk is missing a newline, causing drm debug logs to be hard to read. Add a newline so that the message is on its own line. Cc: Simon Ser <contact@emersion.fr> Cc: Pekka Paalanen <pekka.paalanen@collabora.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Fixes: 8f86c82aba8b ("drm/connector: demote connector force-probes for non-master clients") Signed-off-by: Stephen Boyd <swboyd@chromium.org> --- drivers/gpu/drm/drm_connector.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c index 3ed4cfcb350c..ab1467a15f9a 100644 --- a/drivers/gpu/drm/drm_connector.c +++ b/drivers/gpu/drm/drm_connector.c @@ -2923,7 +2923,7 @@ int drm_mode_getconnector(struct drm_device *dev, void *data, dev->mode_config.max_width, dev->mode_config.max_height); else - drm_dbg_kms(dev, "User-space requested a forced probe on [CONNECTOR:%d:%s] but is not the DRM master, demoting to read-only probe", + drm_dbg_kms(dev, "User-space requested a forced probe on [CONNECTOR:%d:%s] but is not the DRM master, demoting to read-only probe\n", connector->base.id, connector->name); } base-commit: 706a741595047797872e669b3101429ab8d378ef -- https://chromeos.dev
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <swboyd@chromium.org> To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com> Cc: Pekka Paalanen <pekka.paalanen@collabora.com>, Daniel Vetter <daniel.vetter@ffwll.ch>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, patches@lists.linux.dev Subject: [PATCH] drm/connector: Add newline to debug printk Date: Fri, 25 Aug 2023 16:31:17 -0700 [thread overview] Message-ID: <20230825233118.2689222-1-swboyd@chromium.org> (raw) This debug printk is missing a newline, causing drm debug logs to be hard to read. Add a newline so that the message is on its own line. Cc: Simon Ser <contact@emersion.fr> Cc: Pekka Paalanen <pekka.paalanen@collabora.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Fixes: 8f86c82aba8b ("drm/connector: demote connector force-probes for non-master clients") Signed-off-by: Stephen Boyd <swboyd@chromium.org> --- drivers/gpu/drm/drm_connector.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c index 3ed4cfcb350c..ab1467a15f9a 100644 --- a/drivers/gpu/drm/drm_connector.c +++ b/drivers/gpu/drm/drm_connector.c @@ -2923,7 +2923,7 @@ int drm_mode_getconnector(struct drm_device *dev, void *data, dev->mode_config.max_width, dev->mode_config.max_height); else - drm_dbg_kms(dev, "User-space requested a forced probe on [CONNECTOR:%d:%s] but is not the DRM master, demoting to read-only probe", + drm_dbg_kms(dev, "User-space requested a forced probe on [CONNECTOR:%d:%s] but is not the DRM master, demoting to read-only probe\n", connector->base.id, connector->name); } base-commit: 706a741595047797872e669b3101429ab8d378ef -- https://chromeos.dev
next reply other threads:[~2023-08-25 23:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-25 23:31 Stephen Boyd [this message] 2023-08-25 23:31 ` [PATCH] drm/connector: Add newline to debug printk Stephen Boyd 2023-08-25 23:32 ` Simon Ser 2023-08-25 23:32 ` Simon Ser
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=20230825233118.2689222-1-swboyd@chromium.org \ --to=swboyd@chromium.org \ --cc=airlied@gmail.com \ --cc=contact@emersion.fr \ --cc=daniel.vetter@ffwll.ch \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=mripard@kernel.org \ --cc=patches@lists.linux.dev \ --cc=pekka.paalanen@collabora.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.