From: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Michael Kelley <mhklinux@outlook.com>,
"deller@gmx.de" <deller@gmx.de>, "arnd@arndb.de" <arnd@arndb.de>,
"soci@c64.rulez.org" <soci@c64.rulez.org>,
"gonzalo.silvalde@gmail.com" <gonzalo.silvalde@gmail.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"bartosz.golaszewski@linaro.org" <bartosz.golaszewski@linaro.org>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
"ssengar@linux.microsoft.com" <ssengar@linux.microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [RFC 1/3] fbdev: hyperv_fb: Remove hyperv_fb driver
Date: Tue, 16 Sep 2025 10:07:06 +0530 [thread overview]
Message-ID: <b723ad91-e1ce-4b8d-8a0f-32ace00ad619@linux.microsoft.com> (raw)
In-Reply-To: <d452d75a-5a0a-42c2-9ea1-fcd08b09176c@suse.de>
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
next prev parent reply other threads:[~2025-09-16 4:37 UTC|newest]
Thread overview: 11+ 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 [this message]
2025-09-11 16:23 ` Prasanna Kumar T S M
2025-09-09 16:58 ` [RFC 2/3] drm/hyperv: Remove reference to " Prasanna Kumar T S M
2025-09-09 16:59 ` [RFC 3/3] Drivers: hv: vmbus_drv: Remove reference to hyperv_fb Prasanna Kumar T S M
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=b723ad91-e1ce-4b8d-8a0f-32ace00ad619@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