All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Gurchetan Singh <gurchetansingh@chromium.org>
Cc: virtio-comment@lists.oasis-open.org, olvaffe@gmail.com
Subject: [virtio-comment] Re: [PATCH v1 1/2] virtio-gpu: clarify spec regarding capability sets
Date: Wed, 15 Sep 2021 10:20:32 +0200	[thread overview]
Message-ID: <20210915082032.rdyas25ngy42ifwp@sirius.home.kraxel.org> (raw)
In-Reply-To: <20210909012953.431-1-gurchetansingh@chromium.org>

On Wed, Sep 08, 2021 at 06:29:52PM -0700, Gurchetan Singh wrote:
> Capability sets will be used as a proxy for the context type,
> so add more detail regarding their use.
> 
> Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>

Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


      parent reply	other threads:[~2021-09-15  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  1:29 [virtio-comment] [PATCH v1 1/2] virtio-gpu: clarify spec regarding capability sets Gurchetan Singh
2021-09-09  1:29 ` [virtio-comment] [PATCH v1 2/2] virtio-gpu: add context init support Gurchetan Singh
2021-09-15  8:20   ` [virtio-comment] " Gerd Hoffmann
2021-09-15 23:37     ` Gurchetan Singh
2021-09-15  8:20 ` Gerd Hoffmann [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=20210915082032.rdyas25ngy42ifwp@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=gurchetansingh@chromium.org \
    --cc=olvaffe@gmail.com \
    --cc=virtio-comment@lists.oasis-open.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 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.