From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
Sui Jingfeng <suijingfeng@loongson.cn>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Li Yi <liyi@loongson.cn>,
Christian Koenig <christian.koenig@amd.com>,
Helge Deller <deller@gmx.de>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] video/aperture: fix typos
Date: Tue, 4 Apr 2023 13:08:45 +0200 [thread overview]
Message-ID: <bf2aedc8-5055-a931-65bc-e153f74e737c@suse.de> (raw)
In-Reply-To: <87355fex1f.fsf@minerva.mail-host-address-is-not-set>
[-- Attachment #1.1: Type: text/plain, Size: 1918 bytes --]
Hi
Am 04.04.23 um 12:55 schrieb Javier Martinez Canillas:
> Thomas Zimmermann <tzimmermann@suse.de> writes:
>
> Hello Thomas,
>
> Sorry, I just applied this patch and didn't see your email before...
>
>> Hi
>>
>> Am 04.04.23 um 06:01 schrieb Sui Jingfeng:
>>> EFI FB, VESA FB or VGA FB etc are belong to firmware based framebuffer
>>> driver.
>>
>> No whitespaces at the beginning of the lines.
>>
>
> I fixed that before applying, also removed the "are" in the sentence
> above, since it sounded off and repharsed subject line as "Fix typos
> in comments".
>
> [...]
>
>>> /*
>>> * Remove the device from the device hierarchy. This is the right thing
>>> - * to do for firmware-based DRM drivers, such as EFI, VESA or VGA. After
>>> + * to do for firmware-based fb drivers, such as EFI, VESA or VGA. After
>>
>> That sentences is not well phrased. Maybe say 'This is required for
>> firmware-provided graphics, such as EFI, VESA or VGA.'
>>
>
> Graphic drivers or display drivers would indeed be more accurate here. But
> I think that "fb drivers" is still well pharsed since the are other places
> where either fbdev or DRM drivers for firmware-provided framebuffers are
> named like that.
I meant my original comment when I said 'not well phrased'. It's not
Jingfeng's fault, but in my original text. Removing the device is
required for scanout buffers that have been provided by the firmware.
The attached graphics driver is secondary to this. But I'm struggling to
find a simple sentence to express this. :/
Best regards
Thomas
>
> For example, in the sysfb platform code and Kconfig symbol help text.
>
>> Best regards
>> Thomas
>>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-04-04 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 4:01 Sui Jingfeng
2023-04-04 10:05 ` Javier Martinez Canillas
2023-04-04 10:48 ` Javier Martinez Canillas
2023-04-04 10:41 ` Thomas Zimmermann
2023-04-04 10:55 ` Javier Martinez Canillas
2023-04-04 11:03 ` Javier Martinez Canillas
2023-04-05 9:55 ` Sui Jingfeng
2023-04-05 10:36 ` Sui Jingfeng
2023-04-04 11:08 ` Thomas Zimmermann [this message]
2023-05-12 15:09 ` Pavel Machek
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=bf2aedc8-5055-a931-65bc-e153f74e737c@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liyi@loongson.cn \
--cc=lucas.demarchi@intel.com \
--cc=mripard@kernel.org \
--cc=suijingfeng@loongson.cn \
/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®