linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev@vger.kernel.org, kvm@vger.kernel.org,
	linux-hyperv@vger.kernel.org, linux-sh@vger.kernel.org,
	deller@gmx.de, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	javierm@redhat.com, dri-devel@lists.freedesktop.org,
	linux-input@vger.kernel.org, linux-nvidia@lists.surfsouth.com,
	linux-omap@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-geode@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3 00/18] fbdev: Remove FBINFO_DEFAULT and FBINFO_FLAG_DEFAULT flags
Date: Fri, 14 Jul 2023 12:24:05 +0200	[thread overview]
Message-ID: <47a3ab8d-5e8c-db2c-fcde-5c2b1bac32aa@suse.de> (raw)
In-Reply-To: <CAMuHMdWoeyJPAgPgFi545SJFcaVCgZi1-zW2N5cBeU9BnHgo1w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2237 bytes --]

Hi

Am 14.07.23 um 12:04 schrieb Geert Uytterhoeven:
> Hi Thomas,
> 
> On Fri, Jul 14, 2023 at 9:53 AM Thomas Zimmermann <tzimmermann@suse.de> wrote:
>> Remove the unused flags FBINFO_DEFAULT and FBINFO_FLAG_DEFAULT from
>> fbdev and drivers, as briefly discussed at [1]. Both flags were maybe
>> useful when fbdev had special handling for driver modules. With
>> commit 376b3ff54c9a ("fbdev: Nuke FBINFO_MODULE"), they are both 0
>> and have no further effect.
>>
>> Patches 1 to 7 remove FBINFO_DEFAULT from drivers. Patches 2 to 5
>> split this by the way the fb_info struct is being allocated. All flags
>> are cleared to zero during the allocation.
>>
>> Patches 8 to 16 do the same for FBINFO_FLAG_DEFAULT. Patch 8 fixes
>> an actual bug in how arch/sh uses the token for struct fb_videomode,
>> which is unrelated.
>>
>> Patch 17 removes both flag constants from <linux/fb.h> and patch 18
>> documents the zero'ed memory returned by framebuffer_alloc().
>>
>> v3:
>>          * sh: include board name in commit message (Adrian)
>>          * docs: reword text (Miguel)
> 
> Thanks for the update!
> 
>>    fbdev: Remove flag FBINFO_DEFAULT from fbdev drivers
>>    fbdev: Remove flag FBINFO_DEFAULT from fbdev drivers
>>    fbdev: Remove flag FBINFO_DEFAULT from fbdev drivers
>>    fbdev: Remove flag FBINFO_DEFAULT from fbdev drivers

I wasn't happy about this either. But I could not come up with a 
description that fits into the 74-char limit for each commit. They only 
differ in the method of memory allocation. Do you have any ideas?

> 
> Four patches with the exact same one-line summary. Please make them
> unique.
> 
>>    fbdev: Remove flag FBINFO_FLAG_DEFAULT from fbdev drivers
>>    fbdev: Remove flag FBINFO_FLAG_DEFAULT from fbdev drivers
> 
> Two patches with the exact same one-line summary. Please make them
> unique.

Same problem here.

Best regards
Thomas

> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-07-14 10:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  7:49 [PATCH v3 00/18] fbdev: Remove FBINFO_DEFAULT and FBINFO_FLAG_DEFAULT flags Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 01/18] drm: Remove flag FBINFO_DEFAULT from fbdev emulation Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 02/18] fbdev: Remove flag FBINFO_DEFAULT from fbdev drivers Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 03/18] " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 04/18] " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 05/18] " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 06/18] fbdev/fsl-diu-fb: Remove flag FBINFO_DEFAULT Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 07/18] vfio-mdev: Remove flag FBINFO_DEFAULT from fbdev sample driver Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 08/18] sh: mach-sh7763rdp: Assign FB_MODE_IS_UNKNOWN to struct fb_videomode.flag Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 09/18] auxdisplay: Remove flag FBINFO_FLAG_DEFAULT from fbdev drivers Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 10/18] hid/picolcd: Remove flag FBINFO_FLAG_DEFAULT from fbdev driver Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 11/18] media: Remove flag FBINFO_FLAG_DEFAULT from fbdev drivers Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 12/18] staging: " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 13/18] fbdev: " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 14/18] " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 15/18] fbdev/atafb: Remove flag FBINFO_FLAG_DEFAULT Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 16/18] fbdev/pxafb: " Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 17/18] fbdev: Remove FBINFO_DEFAULT and FBINFO_FLAG_DEFAULT Thomas Zimmermann
2023-07-14  7:49 ` [PATCH v3 18/18] fbdev: Document that framebuffer_alloc() returns zero'ed data Thomas Zimmermann
2023-07-14 10:17   ` [v3,18/18] " Sui JIngfeng
2023-07-14 10:04 ` [PATCH v3 00/18] fbdev: Remove FBINFO_DEFAULT and FBINFO_FLAG_DEFAULT flags Geert Uytterhoeven
2023-07-14 10:24   ` Thomas Zimmermann [this message]
2023-07-14 10:29     ` Dan Carpenter
2023-07-14 10:47       ` Thomas Zimmermann

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=47a3ab8d-5e8c-db2c-fcde-5c2b1bac32aa@suse.de \
    --to=tzimmermann@suse.de \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=javierm@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-nvidia@lists.surfsouth.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).