From: Lyude Paul <lyude@redhat.com>
To: Julia Lawall <Julia.Lawall@inria.fr>, Ben Skeggs <bskeggs@redhat.com>
Cc: kernel-janitors@vger.kernel.org,
Karol Herbst <kherbst@redhat.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/nouveau/mmu: fix typo in comment
Date: Mon, 23 May 2022 15:52:11 -0400 [thread overview]
Message-ID: <70daebd6d65b34f5ab85f0286df9a539b5c62146.camel@redhat.com> (raw)
In-Reply-To: <20220521111145.81697-57-Julia.Lawall@inria.fr>
Reviewed-by: Lyude Paul <lyude@redhat.com>
Will fix that double space after the punctuation while I'm at it as well, and
will push to the appropriate branch in a little bit. Thanks!
On Sat, 2022-05-21 at 13:11 +0200, Julia Lawall wrote:
> Spelling mistake (triple letters) in comment.
> Detected with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>
> ---
> drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c
> b/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c
> index 8bf00b396ec1..8b11dfa0998d 100644
> --- a/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c
> +++ b/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c
> @@ -280,7 +280,7 @@ nvkm_vmm_unref_ptes(struct nvkm_vmm_iter *it, bool pfn,
> u32 ptei, u32 ptes)
> if (desc->type == SPT && (pgt->refs[0] || pgt->refs[1]))
> nvkm_vmm_unref_sptes(it, pgt, desc, ptei, ptes);
>
> - /* PT no longer neeed? Destroy it. */
> + /* PT no longer needed? Destroy it. */
> if (!pgt->refs[type]) {
> it->lvl++;
> TRA(it, "%s empty", nvkm_vmm_desc_type(desc));
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
prev parent reply other threads:[~2022-05-23 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 11:11 [PATCH] drm/nouveau/mmu: fix typo in comment Julia Lawall
2022-05-23 19:52 ` Lyude Paul [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=70daebd6d65b34f5ab85f0286df9a539b5c62146.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Julia.Lawall@inria.fr \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@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;
as well as URLs for NNTP newsgroup(s).