From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: sunliming <sunliming@kylinos.cn>, <christian.koenig@amd.com>,
<robdclark@gmail.com>, <dmitry.baryshkov@linaro.org>
Cc: <freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <kelulanainsley@gmail.com>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH RESEND] drm/msm/dsi: fix the inconsistent indenting
Date: Fri, 8 Jul 2022 09:03:43 -0700 [thread overview]
Message-ID: <57d342b6-6254-9bb0-da80-a2f6b4d5eefe@quicinc.com> (raw)
In-Reply-To: <20220708005832.439722-1-sunliming@kylinos.cn>
On 7/7/2022 5:58 PM, sunliming wrote:
> Fix the inconsistent indenting in function msm_dsi_dphy_timing_calc_v3().
>
> Fix the following smatch warnings:
>
> drivers/gpu/drm/msm/dsi/phy/dsi_phy.c:350 msm_dsi_dphy_timing_calc_v3() warn: inconsistent indenting
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: sunliming <sunliming@kylinos.cn>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> ---
> drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/dsi/phy/dsi_phy.c b/drivers/gpu/drm/msm/dsi/phy/dsi_phy.c
> index a39de3bdc7fa..56dfa2d24be1 100644
> --- a/drivers/gpu/drm/msm/dsi/phy/dsi_phy.c
> +++ b/drivers/gpu/drm/msm/dsi/phy/dsi_phy.c
> @@ -347,7 +347,7 @@ int msm_dsi_dphy_timing_calc_v3(struct msm_dsi_dphy_timing *timing,
> } else {
> timing->shared_timings.clk_pre =
> linear_inter(tmax, tmin, pcnt2, 0, false);
> - timing->shared_timings.clk_pre_inc_by_2 = 0;
> + timing->shared_timings.clk_pre_inc_by_2 = 0;
> }
>
> timing->ta_go = 3;
next prev parent reply other threads:[~2022-07-08 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 0:58 [PATCH RESEND] drm/msm/dsi: fix the inconsistent indenting sunliming
2022-07-08 16:03 ` Abhinav Kumar [this message]
2022-07-18 18:21 ` [Freedreno] " Abhinav Kumar
2022-07-19 1:56 sunliming
2022-08-26 8:49 sunliming
2022-08-26 9:09 ` Dmitry Baryshkov
2022-08-26 16:10 ` Abhinav Kumar
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=57d342b6-6254-9bb0-da80-a2f6b4d5eefe@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=christian.koenig@amd.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=freedreno@lists.freedesktop.org \
--cc=kelulanainsley@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=robdclark@gmail.com \
--cc=sunliming@kylinos.cn \
/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).