From: Zack Rusin <zackr@vmware.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"kamil.konieczny@linux.intel.com"
<kamil.konieczny@linux.intel.com>
Cc: Martin Krastev <krastevm@vmware.com>,
"contact@emersion.fr" <contact@emersion.fr>
Subject: Re: [igt-dev] [PATCH i-g-t v1 5/5] drm-uapi: sync virtgpu and vmwgfx with drm-next
Date: Tue, 24 Oct 2023 17:09:16 +0000 [thread overview]
Message-ID: <e66d8ebe0b5fbc51f8454220926716091486debd.camel@vmware.com> (raw)
In-Reply-To: <20231023141951.32425-6-kamil.konieczny@linux.intel.com>
On Mon, 2023-10-23 at 16:19 +0200, Kamil Konieczny wrote:
> From: Simon Ser <contact@emersion.fr>
>
> Sync drm-uapi headers virtgpu and vmwgfx with
> drm-next commit ("52920704df878050123dfeb469aa6ab8022547c1")
>
> v1: split virtgpu and vmwgfx to separete patch (Kamil)
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Cc: Roye Eshed <reshed@vmware.com>
> Cc: Zack Rusin <zackr@vmware.com>
> Cc: Martin Krastev <krastevm@vmware.com>
The vmw parts look good.
Acked-by: Zack Rusin <zackr@vmware.com>
prev parent reply other threads:[~2023-10-24 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 14:19 [igt-dev] [PATCH i-g-t v1 0/5] drm-uapi: sync with drm-next 52920704df87 Kamil Konieczny
2023-10-23 14:19 ` [igt-dev] [PATCH i-g-t v1 1/5] drm-uapi/amdgpu_drm: sync with drm-next Kamil Konieczny
2023-10-23 15:44 ` Deucher, Alexander
2023-10-23 14:19 ` [igt-dev] [PATCH i-g-t v1 2/5] drm-uapi/i915_drm: " Kamil Konieczny
2023-10-25 14:03 ` Kumar, Janga Rahul
2023-10-23 14:19 ` [igt-dev] [PATCH i-g-t v1 3/5] drm-uapi/msm: " Kamil Konieczny
2023-10-25 14:23 ` Kumar, Janga Rahul
2023-10-23 14:19 ` [igt-dev] [PATCH i-g-t v1 4/5] drm-uapi/panfrost: " Kamil Konieczny
2023-10-25 14:25 ` Kumar, Janga Rahul
2023-10-23 14:19 ` [igt-dev] [PATCH i-g-t v1 5/5] drm-uapi: sync virtgpu and vmwgfx " Kamil Konieczny
2023-10-24 17:09 ` Zack Rusin [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=e66d8ebe0b5fbc51f8454220926716091486debd.camel@vmware.com \
--to=zackr@vmware.com \
--cc=contact@emersion.fr \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=krastevm@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox