From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: alexander.deucher@amd.com
Cc: christian.koenig@amd.com, Xinhui.Pan@amd.com, airlied@linux.ie,
daniel@ffwll.ch, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: [PATCH 02/20] drm/amd/display: Clean up some inconsistent indenting
Date: Tue, 26 Jul 2022 15:25:37 +0800 [thread overview]
Message-ID: <20220726072555.91323-2-jiapeng.chong@linux.alibaba.com> (raw)
In-Reply-To: <20220726072555.91323-1-jiapeng.chong@linux.alibaba.com>
No functional modification involved.
smatch warnings:
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_mpc.c:306 mpc32_get_shaper_current() warn: inconsistent indenting.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
.../gpu/drm/amd/display/dc/dcn32/dcn32_mpc.c | 36 +++++++++----------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_mpc.c b/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_mpc.c
index 94141f5e6994..357bd2461bc9 100644
--- a/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_mpc.c
+++ b/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_mpc.c
@@ -300,24 +300,24 @@ static enum dc_lut_mode mpc32_get_shaper_current(struct mpc *mpc, uint32_t mpcc_
uint32_t state_mode;
struct dcn30_mpc *mpc30 = TO_DCN30_MPC(mpc);
- REG_GET(MPCC_MCM_SHAPER_CONTROL[mpcc_id],
- MPCC_MCM_SHAPER_MODE_CURRENT, &state_mode);
-
- switch (state_mode) {
- case 0:
- mode = LUT_BYPASS;
- break;
- case 1:
- mode = LUT_RAM_A;
- break;
- case 2:
- mode = LUT_RAM_B;
- break;
- default:
- mode = LUT_BYPASS;
- break;
- }
- return mode;
+ REG_GET(MPCC_MCM_SHAPER_CONTROL[mpcc_id], MPCC_MCM_SHAPER_MODE_CURRENT, &state_mode);
+
+ switch (state_mode) {
+ case 0:
+ mode = LUT_BYPASS;
+ break;
+ case 1:
+ mode = LUT_RAM_A;
+ break;
+ case 2:
+ mode = LUT_RAM_B;
+ break;
+ default:
+ mode = LUT_BYPASS;
+ break;
+ }
+
+ return mode;
}
--
2.20.1.7.g153144c
next prev parent reply other threads:[~2022-07-26 7:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 7:25 [PATCH 01/20] " Jiapeng Chong
2022-07-26 7:25 ` Jiapeng Chong [this message]
2022-07-26 7:25 ` [PATCH 03/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 04/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 05/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 06/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 07/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 08/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 09/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 10/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 11/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 12/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 13/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 14/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 15/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 16/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 17/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 18/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 19/20] " Jiapeng Chong
2022-07-26 7:25 ` [PATCH 20/20] " Jiapeng Chong
2022-07-26 15:12 ` [PATCH 01/20] " Alex Deucher
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=20220726072555.91323-2-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=Xinhui.Pan@amd.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®