From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>,
Rob Clark <robdclark@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>,
<linux-arm-msm@vger.kernel.org>,
<freedreno@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Vinod Polimera <quic_vpolimer@quicinc.com>
Subject: Re: [PATCH] drm/msm/dp: Add newlines to debug printks
Date: Fri, 25 Aug 2023 16:57:51 -0700 [thread overview]
Message-ID: <c229f00b-5e8b-b010-70bd-3478216c65a3@quicinc.com> (raw)
In-Reply-To: <20230825230109.2264345-1-swboyd@chromium.org>
On 8/25/2023 4:01 PM, Stephen Boyd wrote:
> These debug printks are missing newlines, causing drm debug logs to be
> hard to read. Add newlines so that the messages are on their own line.
>
> Cc: Kuogee Hsieh <quic_khsieh@quicinc.com>
> Cc: Vinod Polimera <quic_vpolimer@quicinc.com>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> drivers/gpu/drm/msm/dp/dp_link.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/dp/dp_link.c b/drivers/gpu/drm/msm/dp/dp_link.c
> index 42427129acea..6375daaeb98e 100644
> --- a/drivers/gpu/drm/msm/dp/dp_link.c
> +++ b/drivers/gpu/drm/msm/dp/dp_link.c
> @@ -1090,7 +1090,7 @@ int dp_link_process_request(struct dp_link *dp_link)
> } else if (dp_link_read_psr_error_status(link)) {
> DRM_ERROR("PSR IRQ_HPD received\n");
> } else if (dp_link_psr_capability_changed(link)) {
> - drm_dbg_dp(link->drm_dev, "PSR Capability changed");
> + drm_dbg_dp(link->drm_dev, "PSR Capability changed\n");
> } else {
> ret = dp_link_process_link_status_update(link);
> if (!ret) {
> @@ -1107,7 +1107,7 @@ int dp_link_process_request(struct dp_link *dp_link)
> }
> }
>
> - drm_dbg_dp(link->drm_dev, "sink request=%#x",
> + drm_dbg_dp(link->drm_dev, "sink request=%#x\n",
> dp_link->sink_request);
perhaps we can move sink_request to the previous line itself with this
patch and we can avoid the line break.
But thats a very minor comment, otherwise LGTM
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> return ret;
> }
>
> base-commit: 706a741595047797872e669b3101429ab8d378ef
prev parent reply other threads:[~2023-08-25 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 23:01 [PATCH] drm/msm/dp: Add newlines to debug printks Stephen Boyd
2023-08-25 23:30 ` Dmitry Baryshkov
2023-08-25 23:57 ` Abhinav Kumar [this message]
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=c229f00b-5e8b-b010-70bd-3478216c65a3@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=quic_khsieh@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=robdclark@gmail.com \
--cc=swboyd@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;
as well as URLs for NNTP newsgroup(s).