From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
sima@ffwll.ch, airlied@gmail.com
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: sysfb: Mark CONFIG_SYSFB_SIMPLEFB as deprecated
Date: Wed, 17 Jun 2026 10:57:28 +0200 [thread overview]
Message-ID: <eeb2102f-2e27-41d3-bb50-c0f64b6f47c3@suse.de> (raw)
In-Reply-To: <877bnxzh9s.fsf@ocarina.mail-host-address-is-not-set>
Hi
Am 17.06.26 um 10:46 schrieb Javier Martinez Canillas:
> Thomas Zimmermann <tzimmermann@suse.de> writes:
>
> Hello Thomas,
>
> Thanks for the patch.
>
>> Mark CONFIG_SYSFB_SIMPLEFB as deprecated. Enabling it allows to
>> run simpledrm and simplefb on EFI/VESA framebuffers. Doing this
>> is discouraged in favor of using efidrm and vesadrm.
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> ---
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Thanks. The sashiko bot detected some inconsistencies in the docs, so
there will be a v2 of this patch.
>
> Do you know what the policy is for removal? For example,
> how many Linux releases should we wait for this to go away?
IDK. I'd wait for 2 or 3 releases after this lands and then remove it.
It's a small change with a clear upgrade patch after all.
Best regards
Thomas
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-06-17 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 8:17 [PATCH] firmware: sysfb: Mark CONFIG_SYSFB_SIMPLEFB as deprecated Thomas Zimmermann
2026-06-17 8:46 ` Javier Martinez Canillas
2026-06-17 8:57 ` Thomas Zimmermann [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=eeb2102f-2e27-41d3-bb50-c0f64b6f47c3@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sima@ffwll.ch \
/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