[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3871c05-7cab-57ae-592c-1cfcba4e61af@quicinc.com>
Date: Wed, 6 Sep 2023 13:29:54 -0700
From: Abhinav Kumar <quic_abhinavk@...cinc.com>
To: Jim Cromie <jim.cromie@...il.com>, <linux-kernel@...r.kernel.org>,
<dri-devel@...ts.freedesktop.org>, <amd-gfx@...ts.freedesktop.org>,
<intel-gvt-dev@...ts.freedesktop.org>,
<intel-gfx@...ts.freedesktop.org>
CC: <daniel.vetter@...ll.ch>, <daniel@...ll.ch>,
<jani.nikula@...el.com>, <ville.syrjala@...ux.intel.com>,
<seanpaul@...omium.org>, <robdclark@...il.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Sean Paul <sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>,
<linux-arm-msm@...r.kernel.org>, <freedreno@...ts.freedesktop.org>
Subject: Re: [PATCH v3 3/5] drm/msm: add trailing newlines to drm_dbg msgs
Hi Jim
On 9/6/2023 12:02 PM, Jim Cromie wrote:
> 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: 207 DRM_DEV_DEBUG,
> 1288 drm_dbg. Clean up the remainders, in maintainer sized chunks.
May I know what 207, 1288 mean here? Is it the number of callers already
having \n?
If so, this might be a big confusing as its subjective to the code-base
you are referring to. So I will just stop with "Most DRM.debug calls
already comport with this".
>
> No functional changes.
>
> Signed-off-by: Jim Cromie <jim.cromie@...il.com>
> ---
> drivers/gpu/drm/msm/msm_fb.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
The change itself LGTM, hence
Reviewed-by: Abhinav Kumar <quic_abhinavk@...cinc.com>
Powered by blists - more mailing lists