From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Kevin Wang <kevin1.wang@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Felix.Kuehling@amd.com, Christian.Koenig@amd.com
Subject: Re: [PATCH] drm/amdgpu: fix amdgpu_bo_release_notify() comment error
Date: Tue, 18 Aug 2020 13:02:30 +0200 [thread overview]
Message-ID: <6a915eec-e4a2-a010-9c4c-d409c3c7ae9b@gmail.com> (raw)
In-Reply-To: <20200817073535.699-1-kevin1.wang@amd.com>
Am 17.08.20 um 09:35 schrieb Kevin Wang:
> fix amdgpu_bo_release_notify() comment error.
>
> Signed-off-by: Kevin Wang <kevin1.wang@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> index 3d95b3edb635..4cb750ed6851 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> @@ -1301,7 +1301,7 @@ void amdgpu_bo_move_notify(struct ttm_buffer_object *bo,
> }
>
> /**
> - * amdgpu_bo_move_notify - notification about a BO being released
> + * amdgpu_bo_release_notify - notification about a BO being released
> * @bo: pointer to a buffer object
> *
> * Wipes VRAM buffers whose contents should not be leaked before the
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-08-18 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 7:35 [PATCH] drm/amdgpu: fix amdgpu_bo_release_notify() comment error Kevin Wang
2020-08-17 8:36 ` Li, Dennis
2020-08-17 8:41 ` Nirmoy
2020-08-17 10:04 ` Christian König
2020-08-18 11:02 ` Christian König [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=6a915eec-e4a2-a010-9c4c-d409c3c7ae9b@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Christian.Koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=kevin1.wang@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