linux-kernel - Re: [RFC 1/3] fbdev: hyperv_fb: Remove hyperv

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b723ad91-e1ce-4b8d-8a0f-32ace00ad619@linux.microsoft.com>
Date: Tue, 16 Sep 2025 10:07:06 +0530
From: Prasanna Kumar T S M <ptsm@...ux.microsoft.com>
To: Thomas Zimmermann <tzimmermann@...e.de>,
 Michael Kelley <mhklinux@...look.com>, "deller@....de" <deller@....de>,
 "arnd@...db.de" <arnd@...db.de>, "soci@....rulez.org" <soci@....rulez.org>,
 "gonzalo.silvalde@...il.com" <gonzalo.silvalde@...il.com>,
 "rdunlap@...radead.org" <rdunlap@...radead.org>,
 "bartosz.golaszewski@...aro.org" <bartosz.golaszewski@...aro.org>,
 "wei.liu@...nel.org" <wei.liu@...nel.org>,
 "ssengar@...ux.microsoft.com" <ssengar@...ux.microsoft.com>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
 "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: Re: [RFC 1/3] fbdev: hyperv_fb: Remove hyperv_fb driver

Hi Thomas,

>>> Is deprecating the driver a mandatory step?
>>>
>> I'm not aware of a mandatory requirement, at least not in the sense
>> of it being documented in Documentation/process like other aspects
>> of the Linux kernel development process. So I would say it's up to
>> the Maintainers for Hyper-V and FBDEV as to whether the Hyper-V
>> FB driver should go through a deprecation phase before being
>> removed.
>>
>> Of course, the purpose of the deprecation phase is to be "nice"
>> to users of the driver by giving them some warning that it is going
>> away. That gives them an opportunity to raise objections, and/or
>> to do any necessary migration to the replacement driver. I suspect
>> there aren't many (or any?) users of Hyper-V FB that can't just move
>> to the Hyper-V DRM driver, but who knows. We might be surprised.
> 
> Let's mark the driver as unmaintained now. There should be a kernel LTS 
> release around December [1], after which hyperv-fb could be removed. 
> Anyone with hard dependencies on hyperv-fb can remain in the LTS for a 
> few more years.

Sure, I will send patch deprecating hyperv_fb driver.

Thanks,
Prasanna