public inbox for amd-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Nirmoy <nirmodas@amd.com>
To: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: fix amdgpu_bo_release_notify() comment error
Date: Mon, 17 Aug 2020 10:41:40 +0200	[thread overview]
Message-ID: <0b07ce69-4c73-9347-2222-eac2c1ab310b@amd.com> (raw)
In-Reply-To: <20200817073535.699-1-kevin1.wang@amd.com>

Acked-by: Nirmoy Das <nirmoy.das@amd.com>

On 8/17/20 9:35 AM, Kevin Wang wrote:
> fix amdgpu_bo_release_notify() comment error.
>
> Signed-off-by: Kevin Wang <kevin1.wang@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

  parent reply	other threads:[~2020-08-17  8:38 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 [this message]
2020-08-17 10:04 ` Christian König
2020-08-18 11:02 ` Christian König

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=0b07ce69-4c73-9347-2222-eac2c1ab310b@amd.com \
    --to=nirmodas@amd.com \
    --cc=amd-gfx@lists.freedesktop.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