From: Sam Ravnborg <sam@ravnborg.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org, Helge Deller <deller@gmx.de>,
Thomas Zimmermann <tzimmermann@suse.de>,
Javier Martinez Canillas <javierm@redhat.com>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
"open list:FRAMEBUFFER LAYER" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] fbdev: Have CONFIG_FB_NOTIFY be tristate
Date: Wed, 8 May 2024 22:36:13 +0200 [thread overview]
Message-ID: <20240508203613.GA2715801@ravnborg.org> (raw)
In-Reply-To: <41639d6b-a429-43f4-8568-12fcd1671cff@app.fastmail.com>
Hi Arnd,
>
> I think if you want to do a new version, that is likely to run
> into new problems, given that this part of fbdev is particularly
> fragile and partly wrong. On the other hand, it would be nice to
> have a patch to limit the use of the notifiers to the smallest
> set of kernel configs that actually need it, and leave it turned
> off for everything else.
>
> These are the ones I could find:
>
> - CONFIG_GUMSTIX_AM200EPD (FB_EVENT_FB_REGISTERED)
I was surprised to see this driver is still around as many other old
drivers was nuked as part of the pxa cleanup.
It is the only user of FB_EVENT_FB_REGISTERED - so a potential cleanup
if the driver is no longer relevant.
Just a drive-by comment, this should not stop a v2 of the patchset.
Sam
next prev parent reply other threads:[~2024-05-08 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 19:28 [PATCH] fbdev: Have CONFIG_FB_NOTIFY be tristate Florian Fainelli
2024-05-03 19:45 ` Arnd Bergmann
2024-05-03 20:22 ` Florian Fainelli
2024-05-06 13:14 ` Daniel Vetter
2024-05-06 14:53 ` Arnd Bergmann
2024-05-06 15:14 ` Arnd Bergmann
2024-05-07 11:10 ` Daniel Vetter
2024-05-07 11:44 ` Arnd Bergmann
2024-05-08 18:37 ` Florian Fainelli
2024-05-08 19:35 ` Arnd Bergmann
2024-05-08 20:36 ` Sam Ravnborg [this message]
2024-05-08 21:05 ` Arnd Bergmann
2024-05-04 11:46 ` kernel test robot
2024-05-04 14:42 ` kernel test robot
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=20240508203613.GA2715801@ravnborg.org \
--to=sam@ravnborg.org \
--cc=arnd@arndb.de \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=florian.fainelli@broadcom.com \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).