From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Irshad, Luqmaan" <Luqmaan.Irshad@amd.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "mst@redhat.com" <mst@redhat.com>,
"alex.bennee@linaro.org" <alex.bennee@linaro.org>,
"odaki@rsg.ci.i.u-tokyo.ac.jp" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
"Pelloux-Prayer,
Pierre-Eric" <Pierre-eric.Pelloux-prayer@amd.com>,
"luckmaan21@gmail.com" <luckmaan21@gmail.com>
Subject: Re: [PATCH] virtio-gpu: create drm fd based on specified render node path
Date: Wed, 10 Dec 2025 18:26:09 +0300 [thread overview]
Message-ID: <8bb35bf8-2efe-485a-92a2-3d06dcab6b76@collabora.com> (raw)
In-Reply-To: <SA1PR12MB94923FF5E9A4A4B8A1F902DC9DA2A@SA1PR12MB9492.namprd12.prod.outlook.com>
On 12/9/25 21:57, Irshad, Luqmaan wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hello Dmitry,
>
> Thats an interesting idea! I would be curious to look into that further, however my ability to do so may be limited since my contract ends at the end of this week.
>
> After my contract ends, I won't have access to a multi-GPU system I can test this on. I may be able to work out some way to borrow the system, but at the moment this is uncertain.
>
> If this patch looks good, my suggestion would be to merge this change, and we can look into adding this as a separate patch on top of this if I can get access to a system. Let me know how this sounds 🙂
>
> Sincerely,
Thanks for notifying that you won't work on the patch further. It will
be merged or amended.
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-12-10 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 18:49 [PATCH] virtio-gpu: create drm fd based on specified render node path Luqmaan Irshad
2025-12-08 0:49 ` Dmitry Osipenko
2025-12-09 18:57 ` Irshad, Luqmaan
2025-12-10 15:26 ` Dmitry Osipenko [this message]
2025-12-11 14:18 ` Akihiko Odaki
2025-12-11 16:30 ` Irshad, Luqmaan
2025-12-12 3:24 ` Akihiko Odaki
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=8bb35bf8-2efe-485a-92a2-3d06dcab6b76@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=Luqmaan.Irshad@amd.com \
--cc=Pierre-eric.Pelloux-prayer@amd.com \
--cc=alex.bennee@linaro.org \
--cc=luckmaan21@gmail.com \
--cc=mst@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).