From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Jani Nikula <jani.nikula@intel.com>, <dri-devel@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/bridge: prefer drm_printf_indent() over inline \t
Date: Wed, 29 Apr 2026 11:23:35 +0530 [thread overview]
Message-ID: <28c0074e-175f-456d-bd6b-d81dd8f9b0b7@intel.com> (raw)
In-Reply-To: <20260408082211.3040194-2-jani.nikula@intel.com>
On 4/8/2026 1:52 PM, Jani Nikula wrote:
> We have a helper drm_printf_indent() for tab indenting the prints. It
> makes the actual strings more readable, and highlights the indented
> parts better in source.
LGTM.
Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/drm_bridge.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
> index d6f512b73389..bac1aae497e0 100644
> --- a/drivers/gpu/drm/drm_bridge.c
> +++ b/drivers/gpu/drm/drm_bridge.c
> @@ -1613,18 +1613,17 @@ static void drm_bridge_debugfs_show_bridge(struct drm_printer *p,
>
> drm_printf(p, "bridge[%u]: %ps\n", idx, bridge->funcs);
>
> - drm_printf(p, "\trefcount: %u%s\n", refcount,
> - lingering ? " [lingering]" : "");
> + drm_printf_indent(p, 1, "refcount: %u%s\n", refcount,
> + lingering ? " [lingering]" : "");
>
> - drm_printf(p, "\ttype: [%d] %s\n",
> - bridge->type,
> - drm_get_connector_type_name(bridge->type));
> + drm_printf_indent(p, 1, "type: [%d] %s\n", bridge->type,
> + drm_get_connector_type_name(bridge->type));
>
> /* The OF node could be freed after drm_bridge_remove() */
> if (bridge->of_node && !lingering)
> - drm_printf(p, "\tOF: %pOFfc\n", bridge->of_node);
> + drm_printf_indent(p, 1, "OF: %pOFfc\n", bridge->of_node);
>
> - drm_printf(p, "\tops: [0x%x]", bridge->ops);
> + drm_printf_indent(p, 1, "ops: [0x%x]", bridge->ops);
> if (bridge->ops & DRM_BRIDGE_OP_DETECT)
> drm_puts(p, " detect");
> if (bridge->ops & DRM_BRIDGE_OP_EDID)
next prev parent reply other threads:[~2026-04-29 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 8:22 [PATCH 1/2] drm/atomic: prefer drm_printf_indent() over inline \t Jani Nikula
2026-04-08 8:22 ` [PATCH 2/2] drm/bridge: " Jani Nikula
2026-04-29 5:53 ` Borah, Chaitanya Kumar [this message]
2026-04-08 16:38 ` ✓ i915.CI.BAT: success for series starting with [1/2] drm/atomic: " Patchwork
2026-04-08 20:04 ` ✓ i915.CI.Full: " Patchwork
2026-04-29 5:51 ` [PATCH 1/2] " Borah, Chaitanya Kumar
2026-04-30 8:05 ` 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=28c0074e-175f-456d-bd6b-d81dd8f9b0b7@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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