All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: virtio-comment@lists.linux.dev, eballetb@redhat.com,
	adelva@google.com, gnurou@gmail.com, cohuck@redhat.com,
	daniel.almeida@collabora.com, ribalda@google.com,
	dverkamp@chromium.org, agordeev@qti.qualcomm.com,
	alex.bennee@linaro.org, nicolas.dufresne@collabora.com,
	gurchetansingh@google.com, changyeon@google.com,
	hverkuil@xs4all.nl, mst@redhat.com
Subject: Re: [PATCH v6 1/1] virtio-media: Add virtio media device specification
Date: Tue, 11 Feb 2025 12:53:58 +0100	[thread overview]
Message-ID: <Z6s6ViQr4rSxYZiI@fedora> (raw)
In-Reply-To: <CADSE00LCgziXZmHs=X60AY6cBnWOEOR8Kyh1AFTFg=b7AHuMqA@mail.gmail.com>

On Tue, Feb 11, 2025 at 10:15:13AM +0100, Albert Esteve wrote:
> On Mon, Feb 10, 2025 at 1:24 PM Matias Ezequiel Vara Larsen
> <mvaralar@redhat.com> wrote:
> >
> > On Wed, Feb 05, 2025 at 04:33:01PM +0100, Albert Esteve wrote:
> > > Virtio-media is an encapsulation of the V4L2 UAPI into
> > > virtio, able to virtualize any video device supported
> > > by V4L2.
> > >
> > > Note that virtio-media does not require the use of a
> > > V4L2 device driver on the host or guest side -
> > > V4L2 is only used as a host-guest protocol,
> > > and both sides are free to convert it from/to any
> > > model that they wish to use.
> > >
> > > Signed-off-by: Albert Esteve <aesteve@redhat.com>
> > > ---
> > >  conformance.tex                           |  13 +-
> > >  content.tex                               |   1 +
> > >  device-types/media/description.tex        | 617 ++++++++++++++++++++++
> > >  device-types/media/device-conformance.tex |  12 +
> > >  device-types/media/driver-conformance.tex |  10 +
> > >  5 files changed, 649 insertions(+), 4 deletions(-)
> >
> > Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> >
> 
> Thanks a lot Matias for your patience and dedication.
> 
> I may wait a few days before trying to move this forward. Either way,
> now I'd need to follow the normal procedure, open a issue and ask for
> a vote here for integration, right?

You can follow the process outlined here:
https://github.com/oasis-tcs/virtio-spec/blob/master/README.md#use-of-github-issues
to get it merged.

Matias


  reply	other threads:[~2025-02-11 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 15:33 [PATCH v6 0/1] virtio-media: Add device specification Albert Esteve
2025-02-05 15:33 ` [PATCH v6 1/1] virtio-media: Add virtio media " Albert Esteve
2025-02-10 12:24   ` Matias Ezequiel Vara Larsen
2025-02-11  9:15     ` Albert Esteve
2025-02-11 11:53       ` Matias Ezequiel Vara Larsen [this message]
2025-02-12 14:39       ` Michael S. Tsirkin
2025-02-14 16:19   ` Alexander Gordeev
2025-02-18  9:49     ` Albert Esteve
2025-02-18 12:31   ` Alexandre Courbot
2025-02-20  9:20     ` Albert Esteve

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=Z6s6ViQr4rSxYZiI@fedora \
    --to=mvaralar@redhat.com \
    --cc=adelva@google.com \
    --cc=aesteve@redhat.com \
    --cc=agordeev@qti.qualcomm.com \
    --cc=alex.bennee@linaro.org \
    --cc=changyeon@google.com \
    --cc=cohuck@redhat.com \
    --cc=daniel.almeida@collabora.com \
    --cc=dverkamp@chromium.org \
    --cc=eballetb@redhat.com \
    --cc=gnurou@gmail.com \
    --cc=gurchetansingh@google.com \
    --cc=hverkuil@xs4all.nl \
    --cc=mst@redhat.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=ribalda@google.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.