From: Geert Uytterhoeven <geert@linux-m68k.org> To: Javier Martinez Canillas <javierm@redhat.com> Cc: Helge Deller <deller@gmx.de>, Jani Nikula <jani.nikula@linux.intel.com>, Thomas Zimmermann <tzimmermann@suse.de>, Daniel Vetter <daniel@ffwll.ch>, Linux Fbdev development list <linux-fbdev@vger.kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, DRI Development <dri-devel@lists.freedesktop.org> Subject: Re: [PATCH] MAINTAINERS: Add Helge as fbdev maintainer Date: Tue, 18 Jan 2022 10:45:00 +0100 [thread overview] Message-ID: <CAMuHMdUWRkMhU1=2V85iqdP8Hec6CoMAy3CwE9SjPhPBjGjuag@mail.gmail.com> (raw) In-Reply-To: <4f65fdd9-4b73-ca83-cf6e-c60c7ccd6558@redhat.com> Hi Javier, On Tue, Jan 18, 2022 at 10:33 AM Javier Martinez Canillas <javierm@redhat.com> wrote: > On 1/18/22 09:54, Helge Deller wrote: > > On 1/18/22 09:38, Jani Nikula wrote: > >> On Mon, 17 Jan 2022, Helge Deller <deller@gmx.de> wrote: > >>> On 1/17/22 22:40, Jani Nikula wrote: > >>>> On Mon, 17 Jan 2022, Thomas Zimmermann <tzimmermann@suse.de> wrote: > >>>>> Seems like few people read linux-fbdev these days. > >>>> > >>>> How much traffic is there to linux-fbdev that is *not* Cc'd to dri-devel > >>>> also? > >>> > >>> Doesn't seem like much traffic - which IMHO is OK for such a tree with > >>> mostly just maintenance patches. > >>> > >>>> Do we still need a separate linux-fbdev mailing list at all? > >>> > >>> Yes. I want to have it seperate of dri-devel. > >>> Actually I'd prefer to drop dri-devel from the list where patches > >>> for fbdev are sent... > >> > >> Disagreed. If anything, this thread shows we can't have fbdev and drm in > >> silos of their own. > > > > Patches to fbdev usually don't affect DRM. > > Patches for fbdev drivers don't usually affect DRM but that's not the > case for patches to fbdev core and fbcon as you and others mentioned. > > > Patches which affect DRM needs to through to dri-devel. > > And how would people know which ones need to go through dri-devel ? Are > you planning to add another entry to MAINTAINERS for fbdev core/fbcon ? Those are nicely contained in drivers/video/fbdev/core/, so an entry in MAINTAINERS listing both linux-fbdev and dri-devel would do. > > In addition this would take the burden of the dri-developers to receive > > unrelated fbdev driver updates and patches. > > In my opinion having fbdev patches in the dri-devel mailing list isn't > a big burden, but rather getting people to review and push say patches. > > Since you are volunteering for the latter, that should improve things. > > I still fail to see the benefit of doing that split, same for having a > separate fbdev tree. Using drm-misc only have advantages, among other > things providing redundancy in cases that a maintainer isn't available > for a period of time. The above is the point of view from a DRM developer? For an fbdev developer, the burden to receive unrelated DRM driver updates and patches would be significant. The first page of https://lore.kernel.org/dri-devel/ goes back to yesterday. The first page of https://lore.kernel.org/linux-fbdev/ goes back to Nov 30th. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Javier Martinez Canillas <javierm@redhat.com> Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Helge Deller <deller@gmx.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, DRI Development <dri-devel@lists.freedesktop.org>, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: [PATCH] MAINTAINERS: Add Helge as fbdev maintainer Date: Tue, 18 Jan 2022 10:45:00 +0100 [thread overview] Message-ID: <CAMuHMdUWRkMhU1=2V85iqdP8Hec6CoMAy3CwE9SjPhPBjGjuag@mail.gmail.com> (raw) In-Reply-To: <4f65fdd9-4b73-ca83-cf6e-c60c7ccd6558@redhat.com> Hi Javier, On Tue, Jan 18, 2022 at 10:33 AM Javier Martinez Canillas <javierm@redhat.com> wrote: > On 1/18/22 09:54, Helge Deller wrote: > > On 1/18/22 09:38, Jani Nikula wrote: > >> On Mon, 17 Jan 2022, Helge Deller <deller@gmx.de> wrote: > >>> On 1/17/22 22:40, Jani Nikula wrote: > >>>> On Mon, 17 Jan 2022, Thomas Zimmermann <tzimmermann@suse.de> wrote: > >>>>> Seems like few people read linux-fbdev these days. > >>>> > >>>> How much traffic is there to linux-fbdev that is *not* Cc'd to dri-devel > >>>> also? > >>> > >>> Doesn't seem like much traffic - which IMHO is OK for such a tree with > >>> mostly just maintenance patches. > >>> > >>>> Do we still need a separate linux-fbdev mailing list at all? > >>> > >>> Yes. I want to have it seperate of dri-devel. > >>> Actually I'd prefer to drop dri-devel from the list where patches > >>> for fbdev are sent... > >> > >> Disagreed. If anything, this thread shows we can't have fbdev and drm in > >> silos of their own. > > > > Patches to fbdev usually don't affect DRM. > > Patches for fbdev drivers don't usually affect DRM but that's not the > case for patches to fbdev core and fbcon as you and others mentioned. > > > Patches which affect DRM needs to through to dri-devel. > > And how would people know which ones need to go through dri-devel ? Are > you planning to add another entry to MAINTAINERS for fbdev core/fbcon ? Those are nicely contained in drivers/video/fbdev/core/, so an entry in MAINTAINERS listing both linux-fbdev and dri-devel would do. > > In addition this would take the burden of the dri-developers to receive > > unrelated fbdev driver updates and patches. > > In my opinion having fbdev patches in the dri-devel mailing list isn't > a big burden, but rather getting people to review and push say patches. > > Since you are volunteering for the latter, that should improve things. > > I still fail to see the benefit of doing that split, same for having a > separate fbdev tree. Using drm-misc only have advantages, among other > things providing redundancy in cases that a maintainer isn't available > for a period of time. The above is the point of view from a DRM developer? For an fbdev developer, the burden to receive unrelated DRM driver updates and patches would be significant. The first page of https://lore.kernel.org/dri-devel/ goes back to yesterday. The first page of https://lore.kernel.org/linux-fbdev/ goes back to Nov 30th. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2022-01-18 9:45 UTC|newest] Thread overview: 149+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 18:11 [PATCH] MAINTAINERS: Add Helge as fbdev maintainer Helge Deller 2022-01-14 18:31 ` Geert Uytterhoeven 2022-01-14 18:31 ` Geert Uytterhoeven 2022-01-17 9:48 ` Daniel Vetter 2022-01-17 9:48 ` Daniel Vetter 2022-01-17 10:02 ` Daniel Vetter 2022-01-17 10:02 ` Daniel Vetter 2022-01-17 10:19 ` Javier Martinez Canillas 2022-01-17 10:19 ` Javier Martinez Canillas 2022-01-17 10:49 ` Jani Nikula 2022-01-17 10:57 ` Helge Deller 2022-01-17 12:15 ` Helge Deller 2022-01-17 12:15 ` Helge Deller 2022-01-17 12:57 ` Gerd Hoffmann 2022-01-17 12:57 ` Gerd Hoffmann 2022-01-17 13:29 ` Geert Uytterhoeven 2022-01-17 13:29 ` Geert Uytterhoeven 2022-01-17 13:51 ` Thomas Zimmermann 2022-01-17 13:51 ` Thomas Zimmermann 2022-01-17 14:10 ` Geert Uytterhoeven 2022-01-17 14:10 ` Geert Uytterhoeven 2022-01-17 14:47 ` Helge Deller 2022-01-17 14:47 ` Helge Deller 2022-01-17 15:03 ` Daniel Vetter 2022-01-17 15:03 ` Daniel Vetter 2022-01-17 20:17 ` Helge Deller 2022-01-17 20:17 ` Helge Deller 2022-01-18 6:29 ` Gerd Hoffmann 2022-01-18 6:29 ` Gerd Hoffmann 2022-01-18 8:10 ` Geert Uytterhoeven 2022-01-18 8:10 ` Geert Uytterhoeven 2022-01-18 11:44 ` Daniel Vetter 2022-01-18 11:44 ` Daniel Vetter 2022-01-18 14:23 ` Thomas Zimmermann 2022-01-18 14:23 ` Thomas Zimmermann 2022-01-18 14:39 ` Simon Ser 2022-01-18 14:39 ` Simon Ser 2022-01-20 12:50 ` Gerd Hoffmann 2022-01-20 12:50 ` Gerd Hoffmann 2022-01-21 8:55 ` Daniel Vetter 2022-01-21 8:55 ` Daniel Vetter 2022-01-24 18:38 ` Geert Uytterhoeven 2022-01-24 18:38 ` Geert Uytterhoeven 2022-01-24 18:50 ` Daniel Vetter 2022-01-24 18:50 ` Daniel Vetter 2022-01-24 19:05 ` Thomas Zimmermann 2022-01-24 19:05 ` Thomas Zimmermann 2022-01-18 8:20 ` Helge Deller 2022-01-18 8:20 ` Helge Deller 2022-01-18 9:16 ` Gerd Hoffmann 2022-01-18 9:16 ` Gerd Hoffmann 2022-01-18 10:13 ` Helge Deller 2022-01-18 10:13 ` Helge Deller 2022-01-18 10:44 ` Helge Deller 2022-01-18 10:44 ` Helge Deller 2022-01-18 12:48 ` Gerd Hoffmann 2022-01-18 12:48 ` Gerd Hoffmann 2022-01-17 15:05 ` Thomas Zimmermann 2022-01-17 15:05 ` Thomas Zimmermann 2022-01-17 16:05 ` Helge Deller 2022-01-17 16:05 ` Helge Deller 2022-01-17 14:53 ` Thomas Zimmermann 2022-01-17 14:53 ` Thomas Zimmermann 2022-01-18 6:11 ` Gerd Hoffmann 2022-01-18 6:11 ` Gerd Hoffmann 2022-01-18 8:09 ` Helge Deller 2022-01-18 8:09 ` Helge Deller 2022-01-17 15:00 ` Daniel Vetter 2022-01-17 15:00 ` Daniel Vetter 2022-01-17 15:42 ` Helge Deller 2022-01-17 15:42 ` Helge Deller 2022-01-17 15:56 ` Daniel Vetter 2022-01-17 15:56 ` Daniel Vetter 2022-01-17 15:58 ` Thomas Zimmermann 2022-01-17 15:58 ` Thomas Zimmermann 2022-01-17 16:21 ` Helge Deller 2022-01-17 16:21 ` Helge Deller 2022-01-17 16:38 ` Daniel Vetter 2022-01-17 16:38 ` Daniel Vetter 2022-01-17 17:19 ` Helge Deller 2022-01-17 17:19 ` Helge Deller 2022-01-17 19:45 ` Helge Deller 2022-01-17 19:45 ` Helge Deller 2022-01-17 21:55 ` Ilia Mirkin 2022-01-17 21:55 ` Ilia Mirkin 2022-01-18 11:14 ` Daniel Vetter 2022-01-18 11:14 ` Daniel Vetter 2022-01-18 14:14 ` Thomas Zimmermann 2022-01-18 14:14 ` Thomas Zimmermann 2022-01-17 21:40 ` Jani Nikula 2022-01-17 21:40 ` Jani Nikula 2022-01-17 21:44 ` Helge Deller 2022-01-17 21:44 ` Helge Deller 2022-01-18 8:38 ` Jani Nikula 2022-01-18 8:38 ` Jani Nikula 2022-01-18 8:41 ` Geert Uytterhoeven 2022-01-18 8:41 ` Geert Uytterhoeven 2022-01-18 11:41 ` Daniel Vetter 2022-01-18 11:41 ` Daniel Vetter 2022-01-18 12:11 ` Simon Ser 2022-01-18 12:11 ` Simon Ser 2022-01-18 8:54 ` Helge Deller 2022-01-18 8:54 ` Helge Deller 2022-01-18 9:33 ` Javier Martinez Canillas 2022-01-18 9:33 ` Javier Martinez Canillas 2022-01-18 9:45 ` Geert Uytterhoeven [this message] 2022-01-18 9:45 ` Geert Uytterhoeven 2022-01-18 11:18 ` Daniel Vetter 2022-01-18 11:18 ` Daniel Vetter 2022-01-18 11:42 ` Helge Deller 2022-01-18 11:42 ` Helge Deller 2022-01-18 8:41 ` Helge Deller 2022-01-18 8:41 ` Helge Deller 2022-01-18 9:12 ` Helge Deller 2022-01-18 9:12 ` Helge Deller 2022-01-17 11:16 ` Thomas Zimmermann 2022-01-17 11:33 ` Helge Deller 2022-01-17 12:13 ` Thomas Zimmermann 2022-01-17 18:47 ` Sven Schnelle 2022-01-18 8:33 ` Pekka Paalanen 2022-01-18 8:33 ` Pekka Paalanen 2022-01-18 9:53 ` Gerd Hoffmann 2022-01-18 9:53 ` Gerd Hoffmann 2022-01-18 11:22 ` Daniel Vetter 2022-01-18 11:22 ` Daniel Vetter 2022-01-18 12:07 ` Gerd Hoffmann 2022-01-18 12:07 ` Gerd Hoffmann 2022-01-19 8:39 ` Pekka Paalanen 2022-01-19 8:39 ` Pekka Paalanen 2022-01-20 9:06 ` Geert Uytterhoeven 2022-01-20 9:06 ` Geert Uytterhoeven 2022-01-20 11:32 ` Daniel Vetter 2022-01-20 11:32 ` Daniel Vetter 2022-01-20 12:13 ` Geert Uytterhoeven 2022-01-20 12:13 ` Geert Uytterhoeven 2022-01-20 12:33 ` Daniel Vetter 2022-01-20 12:33 ` Daniel Vetter 2022-01-20 12:46 ` Geert Uytterhoeven 2022-01-20 12:46 ` Geert Uytterhoeven 2022-01-24 18:50 ` Geert Uytterhoeven 2022-01-24 18:50 ` Geert Uytterhoeven 2022-01-24 19:37 ` Daniel Vetter 2022-01-24 19:37 ` Daniel Vetter 2022-01-20 11:51 ` Gerd Hoffmann 2022-01-20 11:51 ` Gerd Hoffmann 2022-01-18 8:58 ` Michel Dänzer 2022-01-18 10:05 ` Sven Schnelle 2022-01-18 10:05 ` Sven Schnelle 2022-01-18 14:06 ` 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='CAMuHMdUWRkMhU1=2V85iqdP8Hec6CoMAy3CwE9SjPhPBjGjuag@mail.gmail.com' \ --to=geert@linux-m68k.org \ --cc=daniel@ffwll.ch \ --cc=deller@gmx.de \ --cc=dri-devel@lists.freedesktop.org \ --cc=jani.nikula@linux.intel.com \ --cc=javierm@redhat.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=torvalds@linux-foundation.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.