From: Felix Kuehling <felix.kuehling@amd.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
alexander.deucher@amd.com
Cc: Xinhui.Pan@amd.com, Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, christian.koenig@amd.com
Subject: Re: [PATCH] drm/amdkfd: clean up some inconsistent indenting
Date: Tue, 17 Oct 2023 13:54:25 -0400 [thread overview]
Message-ID: <54dfc01b-bd6b-4cf1-887a-749b45ede088@amd.com> (raw)
In-Reply-To: <20231013032129.55504-1-jiapeng.chong@linux.alibaba.com>
On 2023-10-12 23:21, Jiapeng Chong wrote:
> No functional modification involved.
>
> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_svm.c:305 svm_range_free() warn: inconsistent indenting.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=6804
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
The patch is
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
Applied to amd-staging-drm-next.
Thanks,
Felix
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_svm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_svm.c b/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
> index f4038b33c404..eef76190800c 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
> @@ -302,7 +302,7 @@ static void svm_range_free(struct svm_range *prange, bool do_unmap)
> for (gpuidx = 0; gpuidx < MAX_GPU_INSTANCE; gpuidx++) {
> if (prange->dma_addr[gpuidx]) {
> kvfree(prange->dma_addr[gpuidx]);
> - prange->dma_addr[gpuidx] = NULL;
> + prange->dma_addr[gpuidx] = NULL;
> }
> }
>
prev parent reply other threads:[~2023-10-17 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 3:21 Jiapeng Chong
2023-10-17 17:54 ` Felix Kuehling [this message]
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=54dfc01b-bd6b-4cf1-887a-749b45ede088@amd.com \
--to=felix.kuehling@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=abaci@linux.alibaba.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiapeng.chong@linux.alibaba.com \
--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®