From: "Christian König" <christian.koenig@amd.com>
To: WangYuli <wangyuli@uniontech.com>,
alexander.deucher@amd.com, Xinhui.Pan@amd.com, airlied@gmail.com,
simona@ffwll.ch, sunil.khatri@amd.com, yifan1.zhang@amd.com,
vitaly.prosyak@amd.com, Tim.Huang@amd.com, Prike.Liang@amd.com,
jesse.zhang@amd.com, lijo.lazar@amd.com, Hawking.Zhang@amd.com,
kevinyang.wang@amd.com, srinivasan.shanmugam@amd.com,
victorchengchi.lu@amd.com, Jiadong.Zhu@amd.com,
tao.zhou1@amd.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, le.ma@amd.com,
Wenhui.Sheng@amd.com, alexdeucher@gmail.com,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH] drm/amdgpu: Fix typo "acccess" and improve the comment style here
Date: Fri, 20 Sep 2024 08:28:49 +0200 [thread overview]
Message-ID: <ade271e8-2f6e-494b-979a-e53942b6b9a7@amd.com> (raw)
In-Reply-To: <F25A139789E87C3E+20240920022755.1162495-1-wangyuli@uniontech.com>
Am 20.09.24 um 04:27 schrieb WangYuli:
> There are some spelling mistakes of 'acccess' in comments which
> should be instead of 'access'.
>
> And the comment style should be like this:
> /*
> * Text
> * Text
> */
>
> Suggested-by: Christian König <christian.koenig@amd.com>
> Link: https://lore.kernel.org/all/f75fbe30-528e-404f-97e4-854d27d7a401@amd.com/
> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
> Link: https://lore.kernel.org/all/0c768bf6-bc19-43de-a30b-ff5e3ddfd0b3@suse.de/
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 6 ++++--
> drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c | 6 ++++--
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
> index d3e8be82a172..33fd2da49a2a 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
> @@ -1893,8 +1893,10 @@ static void gfx_v11_0_init_compute_vmid(struct amdgpu_device *adev)
> soc21_grbm_select(adev, 0, 0, 0, 0);
> mutex_unlock(&adev->srbm_mutex);
>
> - /* Initialize all compute VMIDs to have no GDS, GWS, or OA
> - acccess. These should be enabled by FW for target VMIDs. */
> + /*
> + * Initialize all compute VMIDs to have no GDS, GWS, or OA
> + * access. These should be enabled by FW for target VMIDs.
> + */
> for (i = adev->vm_manager.first_kfd_vmid; i < AMDGPU_NUM_VMID; i++) {
> WREG32_SOC15_OFFSET(GC, 0, regGDS_VMID0_BASE, 2 * i, 0);
> WREG32_SOC15_OFFSET(GC, 0, regGDS_VMID0_SIZE, 2 * i, 0);
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c b/drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c
> index 408e5600bb61..57b55b6d797d 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c
> @@ -1247,8 +1247,10 @@ static void gfx_v9_4_3_xcc_init_compute_vmid(struct amdgpu_device *adev,
> soc15_grbm_select(adev, 0, 0, 0, 0, GET_INST(GC, xcc_id));
> mutex_unlock(&adev->srbm_mutex);
>
> - /* Initialize all compute VMIDs to have no GDS, GWS, or OA
> - acccess. These should be enabled by FW for target VMIDs. */
> + /*
> + * Initialize all compute VMIDs to have no GDS, GWS, or OA
> + * access. These should be enabled by FW for target VMIDs.
> + */
> for (i = adev->vm_manager.first_kfd_vmid; i < AMDGPU_NUM_VMID; i++) {
> WREG32_SOC15_OFFSET(GC, GET_INST(GC, xcc_id), regGDS_VMID0_BASE, 2 * i, 0);
> WREG32_SOC15_OFFSET(GC, GET_INST(GC, xcc_id), regGDS_VMID0_SIZE, 2 * i, 0);
next prev parent reply other threads:[~2024-09-20 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 2:27 WangYuli
2024-09-20 6:28 ` Christian König [this message]
2024-09-24 16:08 ` 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=ade271e8-2f6e-494b-979a-e53942b6b9a7@amd.com \
--to=christian.koenig@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=Jiadong.Zhu@amd.com \
--cc=Prike.Liang@amd.com \
--cc=Tim.Huang@amd.com \
--cc=Wenhui.Sheng@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=kevinyang.wang@amd.com \
--cc=le.ma@amd.com \
--cc=lijo.lazar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=srinivasan.shanmugam@amd.com \
--cc=sunil.khatri@amd.com \
--cc=tao.zhou1@amd.com \
--cc=tzimmermann@suse.de \
--cc=victorchengchi.lu@amd.com \
--cc=vitaly.prosyak@amd.com \
--cc=wangyuli@uniontech.com \
--cc=yifan1.zhang@amd.com \
/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®