From: shijie001@208suo.com
To: alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] drm/radeon: ERROR: "(foo*)" should be "(foo *)"
Date: Fri, 14 Jul 2023 13:35:33 +0800 [thread overview]
Message-ID: <26d3424f83f1f394614e2a774d1bf1e9@208suo.com> (raw)
In-Reply-To: <tencent_16FACBDCDA61595C4219E185613C85C8BF0A@qq.com>
Fix one occurrence of the checkpatch.pl error:
ERROR: "(foo*)" should be "(foo *)"
Signed-off-by: Jie Shi <shijie001@208suo.com>
---
drivers/gpu/drm/radeon/uvd_v1_0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon/uvd_v1_0.c
b/drivers/gpu/drm/radeon/uvd_v1_0.c
index 58557c2263a7..5684639d20a6 100644
--- a/drivers/gpu/drm/radeon/uvd_v1_0.c
+++ b/drivers/gpu/drm/radeon/uvd_v1_0.c
@@ -142,7 +142,7 @@ int uvd_v1_0_resume(struct radeon_device *rdev)
addr = (rdev->uvd.gpu_addr >> 32) & 0xFF;
WREG32(UVD_LMI_EXT40_ADDR, addr | (0x9 << 16) | (0x1 << 31));
- WREG32(UVD_FW_START, *((uint32_t*)rdev->uvd.cpu_addr));
+ WREG32(UVD_FW_START, *((uint32_t *)rdev->uvd.cpu_addr));
return 0;
}
next parent reply other threads:[~2023-07-14 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_16FACBDCDA61595C4219E185613C85C8BF0A@qq.com>
2023-07-14 5:35 ` shijie001 [this message]
2023-07-14 7:21 ` Christian König
[not found] <20230710091057.64085-1-xujianghui@cdjrlc.com>
2023-07-10 10:03 ` sunran001
2023-07-10 17:34 ` Alex Deucher
[not found] <20230710082515.54604-1-xujianghui@cdjrlc.com>
2023-07-10 8:26 ` sunran001
2023-07-10 17:25 ` Alex Deucher
[not found] <20230710074943.54300-1-xujianghui@cdjrlc.com>
2023-07-10 7:51 ` sunran001
2023-07-10 17:21 ` 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=26d3424f83f1f394614e2a774d1bf1e9@208suo.com \
--to=shijie001@208suo.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--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®