From: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
deller@gmx.de, arnd@arndb.de, soci@c64.rulez.org,
gonzalo.silvalde@gmail.com, rdunlap@infradead.org,
bartosz.golaszewski@linaro.org, wei.liu@kernel.org,
mhklinux@outlook.com, ssengar@linux.microsoft.com,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [RFC 1/3] fbdev: hyperv_fb: Remove hyperv_fb driver
Date: Thu, 11 Sep 2025 21:53:27 +0530 [thread overview]
Message-ID: <cb823314-f7e4-45ee-bd10-22fcae300a68@linux.microsoft.com> (raw)
In-Reply-To: <8a958fe8-fbba-4bd6-a79d-fd310f08f8d7@suse.de>
Hi Thomas,
On 10-09-2025 15:06, Thomas Zimmermann wrote:
> Hi
>
> Am 09.09.25 um 18:58 schrieb Prasanna Kumar T S M:
>> The Hyper-V DRM driver is available since kernel version 5.14 and
>> provides full KMS support along with fbdev emulation via the DRM fbdev
>> helpers. This makes the hyperv_fb driver redundant, remove it.
>
> I'm all for removing obsolete drivers. But hyperv_drm likely first needs
> to merge the patch at https://lore.kernel.org/dri-
> devel/20250904145806.430568-5-tzimmermann@suse.de/ It's been tested and
> works well. If maintainers from Microsoft have a look at the patch
> first, we could possibly land it fairly soon.
>
I will test those patches on Hyper-V and share the result.
> Best regards
> Thomas
>
prev parent reply other threads:[~2025-09-11 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E2D7F2119CB4>
2025-09-09 16:58 ` [RFC 1/3] fbdev: hyperv_fb: Remove hyperv_fb driver Prasanna Kumar T S M
2025-09-10 9:36 ` Thomas Zimmermann
2025-09-10 15:25 ` Michael Kelley
2025-09-10 15:48 ` Thomas Zimmermann
2025-09-11 16:28 ` Prasanna Kumar T S M
2025-09-12 3:24 ` Michael Kelley
2025-09-12 7:01 ` Thomas Zimmermann
2025-09-16 4:37 ` Prasanna Kumar T S M
2025-09-11 16:23 ` Prasanna Kumar T S M [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=cb823314-f7e4-45ee-bd10-22fcae300a68@linux.microsoft.com \
--to=ptsm@linux.microsoft.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gonzalo.silvalde@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=rdunlap@infradead.org \
--cc=soci@c64.rulez.org \
--cc=ssengar@linux.microsoft.com \
--cc=tzimmermann@suse.de \
--cc=wei.liu@kernel.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).