From: Alyssa Ross <hi@alyssa.is>
To: Gurchetan Singh <gurchetansingh@chromium.org>, qemu-devel@nongnu.org
Cc: kraxel@redhat.com, marcandre.lureau@redhat.com,
akihiko.odaki@gmail.com, dmitry.osipenko@collabora.com,
ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com
Subject: Re: [PATCH v1 0/9] gfxstream + rutabaga_gfx
Date: Mon, 24 Jul 2023 09:56:10 +0000 [thread overview]
Message-ID: <87351diqf9.fsf@alyssa.is> (raw)
In-Reply-To: <20230711025649.708-1-gurchetansingh@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
Gurchetan Singh <gurchetansingh@chromium.org> writes:
> In terms of API stability/versioning/packaging, once this series is
> reviewed, the plan is to cut a "gfxstream upstream release branch". We
> will have the same API guarantees as any other QEMU project then, i.e no
> breaking API changes for 5 years.
What about Rutabaga?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-07-24 9:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 2:56 [PATCH v1 0/9] gfxstream + rutabaga_gfx Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 1/9] virtio: Add shared memory capability Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 2/9] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 3/9] virtio-gpu: hostmem Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 4/9] virtio-gpu: blob prep Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 5/9] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-07-12 11:36 ` Akihiko Odaki
2023-07-11 2:56 ` [PATCH v1 6/9] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-07-12 12:31 ` Akihiko Odaki
2023-07-12 19:14 ` Marc-André Lureau
2023-07-13 1:27 ` Gurchetan Singh
2023-07-15 19:58 ` Bernhard Beschow
2023-07-11 2:56 ` [PATCH v1 7/9] gfxstream + rutabaga: meson support Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 8/9] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-07-11 2:56 ` [PATCH v1 9/9] docs/system: add basic virtio-gpu documentation Gurchetan Singh
2023-07-12 21:40 ` Akihiko Odaki
2023-07-13 1:28 ` Gurchetan Singh
2023-07-24 9:56 ` Alyssa Ross [this message]
2023-07-26 1:10 ` [PATCH v1 0/9] gfxstream + rutabaga_gfx Gurchetan Singh
2023-08-01 15:18 ` Rutabaga backwards compatibility Alyssa Ross
2023-08-05 1:19 ` Gurchetan Singh
2023-08-05 8:47 ` Alyssa Ross
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=87351diqf9.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=shentey@gmail.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 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.