All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.linux.dev, mst@redhat.com,
	cohuck@redhat.com, shahafs@nvidia.com
Subject: Re: [PATCH] virtio-gpu: Fix spelling error
Date: Mon, 28 Oct 2024 10:49:15 +0100	[thread overview]
Message-ID: <Zx9eG4VOSzo1UK7i@fedora> (raw)
In-Reply-To: <20241027044457.495730-1-parav@nvidia.com>

On Sun, Oct 27, 2024 at 06:44:57AM +0200, Parav Pandit wrote:
> Fix spelling error.
> 
> Fixes: fed64230bf31 ("Add virtio gpu device specification.")
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/192
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---

Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>

>  device-types/gpu/description.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/device-types/gpu/description.tex b/device-types/gpu/description.tex
> index ba4ea76..c5706bc 100644
> --- a/device-types/gpu/description.tex
> +++ b/device-types/gpu/description.tex
> @@ -128,7 +128,7 @@ \subsubsection{Device Operation: Create a framebuffer and configure scanout}
>  \item Allocate a framebuffer from guest ram, and attach it as backing
>    storage to the resource just created, using
>    VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING.  Scatter lists are
> -  supported, so the framebuffer doesn't need to be contignous in guest
> +  supported, so the framebuffer doesn't need to be contiguous in guest
>    physical memory.
>  \item Use VIRTIO_GPU_CMD_SET_SCANOUT to link the framebuffer to
>    a display scanout.
> -- 
> 2.34.1
> 


  reply	other threads:[~2024-10-28  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-27  4:44 [PATCH] virtio-gpu: Fix spelling error Parav Pandit
2024-10-28  9:49 ` Matias Ezequiel Vara Larsen [this message]
2024-11-03  5:08   ` Parav Pandit

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=Zx9eG4VOSzo1UK7i@fedora \
    --to=mvaralar@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.