From: Randy Dunlap <rdunlap@infradead.org>
To: Ghanshyam Agrawal <ghanshyam1898@gmail.com>,
zackr@vmware.com, linux-graphics-maintainer@vmware.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: gpu: drm: vmwgfx: fixed typos
Date: Thu, 14 Dec 2023 21:35:43 -0800 [thread overview]
Message-ID: <346d12b2-a78e-4372-880a-e522fdca7169@infradead.org> (raw)
In-Reply-To: <20231215053016.552019-1-ghanshyam1898@gmail.com>
On 12/14/23 21:30, Ghanshyam Agrawal wrote:
> Fixed some typos in vmwgfx_execbuf.c
>
> Signed-off-by: Ghanshyam Agrawal <ghanshyam1898@gmail.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
> index 36987ef3fc30..272141b6164c 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
> @@ -621,10 +621,10 @@ static int vmw_resources_reserve(struct vmw_sw_context *sw_context)
> * @sw_context: Pointer to the software context.
> * @res_type: Resource type.
> * @dirty: Whether to change dirty status.
> - * @converter: User-space visisble type specific information.
> + * @converter: User-space visible type specific information.
ack.
> * @id_loc: Pointer to the location in the command buffer currently being parsed
> * from where the user-space resource id handle is located.
> - * @p_res: Pointer to pointer to resource validalidation node. Populated on
> + * @p_res: Pointer to pointer to resource validation node. Populated on
> * exit.
ack.
> */
> static int
Please also fix this one:
vmwgfx_execbuf.c:1072: asynchronus ==> asynchronous
I suggest that you try codespell.
Thanks.
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
next prev parent reply other threads:[~2023-12-15 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 5:30 Ghanshyam Agrawal
2023-12-15 5:35 ` Randy Dunlap [this message]
2023-12-15 5:53 ` Ghanshyam Agrawal
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=346d12b2-a78e-4372-880a-e522fdca7169@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ghanshyam1898@gmail.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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
all inboxes | Powered by JetHome®