From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org,
Peter Robinson <pbrobinson@gmail.com>,
David Airlie <airlied@linux.ie>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/fb-helper: improve DRM fbdev emulation device names
Date: Fri, 21 May 2021 20:53:56 +0200 [thread overview]
Message-ID: <fc6540fa-1945-a15d-239d-e87bb4d3fa9e@suse.de> (raw)
In-Reply-To: <bfd6fa47-497a-64bc-c2fc-a081bd41d5ec@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]
Hi
Am 21.05.21 um 19:18 schrieb Javier Martinez Canillas:
> On 5/21/21 6:53 PM, Thomas Zimmermann wrote:
>
> [snip]
>
>>>
>>> So what with all the drivers which do _not_ have drm in their name? Also
>>> I'm never sure how much these are uapi or not ...
>>
>
> That someone could threat as an uapi is a fair point indeed.
>
>> Why do we need a suffix anyway?
>>
>
> Yes, I thought the same and was torn about posting a patch to just remove
> the suffix. I don't think users care that much if is a fb device from a
> fbdev driver or a DRM driver using the fbdev emulation.
Yup. I don't see how anything in userspace would depend on the exact
name; especially since fbdev emulation only provides basic features.
(I'd welcome a counter examples that proves me wrong.)
IMHO we can risk it to remove the suffix entirely. But that needs an ack
from Daniel or Dave.
Best regards
Thomas
>
>>> -Daniel
>>>
>
> Best regards,
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-05-21 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 13:19 Javier Martinez Canillas
2021-05-21 15:33 ` Daniel Vetter
2021-05-21 16:53 ` Thomas Zimmermann
2021-05-21 17:18 ` Javier Martinez Canillas
2021-05-21 18:53 ` Thomas Zimmermann [this message]
2021-05-25 13:08 ` Daniel Vetter
2021-05-25 13:34 ` Thomas Zimmermann
2021-05-25 13:52 ` Javier Martinez Canillas
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=fc6540fa-1945-a15d-239d-e87bb4d3fa9e@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pbrobinson@gmail.com \
/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
all inboxes | Powered by JetHome®