From: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"Kim, Dongwon" <dongwon.kim@intel.com>
Subject: RE: [virtio-comment] [PATCH] content: Request to reserve device ID 37 for Dmabuf device
Date: Thu, 4 Feb 2021 23:46:35 +0000 [thread overview]
Message-ID: <62ed2b8a488341e495a3609730ce377c@intel.com> (raw)
In-Reply-To: <20210204111625.4700dd1e.cohuck@redhat.com>
Thank you for the review Cornelia; we'll request a vote soon.
Thanks,
Vivek
> -----Original Message-----
> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Thursday, February 04, 2021 2:16 AM
> To: Kasireddy, Vivek <vivek.kasireddy@intel.com>
> Cc: virtio-comment@lists.oasis-open.org; Kim, Dongwon <dongwon.kim@intel.com>
> Subject: Re: [virtio-comment] [PATCH] content: Request to reserve device ID 37 for
> Dmabuf device
>
> On Wed, 3 Feb 2021 23:46:00 -0800
> Vivek Kasireddy <vivek.kasireddy@intel.com> wrote:
>
> > The Dmabuf device can be used to share a dmabuf created in the Guest
> > with the Host.
> >
> > Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
> > Signed-off-by: Dongwon Kim <dongwon.kim@intel.com>
> > ---
> > content.tex | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/content.tex b/content.tex index 1ca24c1..c1ba683 100644
> > --- a/content.tex
> > +++ b/content.tex
> > @@ -2846,6 +2846,8 @@ \chapter{Device Types}\label{sec:Device Types}
> > \hline
> > 35 & Watchdog \\
> > \hline
> > +37 & Dmabuf device \\
> > +\hline
> > \end{tabular}
> >
> > Some of the devices above are unspecified by this document,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
> In order to request a vote, please follow the process outlined at https://github.com/oasis-
> tcs/virtio-spec#use-of-github-issues.
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/
next prev parent reply other threads:[~2021-02-04 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 8:40 [virtio-comment] [PATCH] virtio-dmabuf: Add specification details for this device Vivek Kasireddy
2021-02-03 10:15 ` Cornelia Huck
2021-02-04 7:46 ` [virtio-comment] [PATCH] content: Request to reserve device ID 37 for Dmabuf device Vivek Kasireddy
2021-02-04 10:16 ` Cornelia Huck
2021-02-04 23:46 ` Kasireddy, Vivek [this message]
2021-02-04 10:24 ` [virtio-comment] [PATCH] virtio-dmabuf: Add specification details for this device Jan Kiszka
2021-02-04 23:43 ` Kasireddy, Vivek
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=62ed2b8a488341e495a3609730ce377c@intel.com \
--to=vivek.kasireddy@intel.com \
--cc=cohuck@redhat.com \
--cc=dongwon.kim@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox