From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Slava Abramov <slava.abramov-5C7GfCeVMHo@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: fix typo in amdgpu_mn.c comments
Date: Wed, 13 Jun 2018 17:01:23 +0200 [thread overview]
Message-ID: <04485ce4-61e4-324f-5734-cd7c8fae7247@gmail.com> (raw)
In-Reply-To: <20180613145651.7352-1-slava.abramov-5C7GfCeVMHo@public.gmane.org>
Am 13.06.2018 um 16:56 schrieb Slava Abramov:
> In doc comments for struct amdgpu_mn: destrution -> destruction
>
> Signed-off-by: Slava Abramov <slava.abramov@amd.com>
Good catch, Reviewed-by: Christian König <christian.koenig@amd.com>.
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
> index 417923ba8de6..b2a9716fa41f 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
> @@ -58,7 +58,7 @@
> * @adev: amdgpu device pointer
> * @mm: process address space
> * @mn: MMU notifier structur
> - * @work: destrution work item
> + * @work: destruction work item
> * @node: hash table node to find structure by adev and mn
> * @lock: rw semaphore protecting the notifier nodes
> * @objects: interval tree containing amdgpu_mn_nodes
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-06-13 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 14:56 [PATCH] drm/amdgpu: fix typo in amdgpu_mn.c comments Slava Abramov
[not found] ` <20180613145651.7352-1-slava.abramov-5C7GfCeVMHo@public.gmane.org>
2018-06-13 15:01 ` 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=04485ce4-61e4-324f-5734-cd7c8fae7247@gmail.com \
--to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=slava.abramov-5C7GfCeVMHo@public.gmane.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