From: Jani Nikula <jani.nikula@linux.intel.com>
To: Helge Deller <deller@gmx.de>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>
Cc: linux-fbdev@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Javier Martinez Canillas <javierm@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] MAINTAINERS: Add Helge as fbdev maintainer
Date: Tue, 18 Jan 2022 10:38:04 +0200 [thread overview]
Message-ID: <87a6ft5thv.fsf@intel.com> (raw)
In-Reply-To: <4f1d6018-d74e-8e62-ea4d-0ca79c6bbbc5@gmx.de>
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.
Also, if the patches continue to get merged through drm-misc, they need
to be sent to dri-devel.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-18 8:38 UTC|newest]
Thread overview: 79+ 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-17 9:48 ` Daniel Vetter
2022-01-17 10:02 ` Daniel Vetter
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:57 ` Gerd Hoffmann
2022-01-17 13:29 ` Geert Uytterhoeven
2022-01-17 13:51 ` Thomas Zimmermann
2022-01-17 14:10 ` Geert Uytterhoeven
2022-01-17 14:47 ` Helge Deller
2022-01-17 15:03 ` Daniel Vetter
2022-01-17 20:17 ` Helge Deller
2022-01-18 6:29 ` Gerd Hoffmann
2022-01-18 8:10 ` Geert Uytterhoeven
2022-01-18 11:44 ` Daniel Vetter
2022-01-18 14:23 ` Thomas Zimmermann
2022-01-18 14:39 ` Simon Ser
2022-01-20 12:50 ` Gerd Hoffmann
2022-01-21 8:55 ` Daniel Vetter
2022-01-24 18:38 ` Geert Uytterhoeven
2022-01-24 18:50 ` Daniel Vetter
2022-01-24 19:05 ` Thomas Zimmermann
2022-01-18 8:20 ` Helge Deller
2022-01-18 9:16 ` Gerd Hoffmann
2022-01-18 10:13 ` Helge Deller
2022-01-18 10:44 ` Helge Deller
2022-01-18 12:48 ` Gerd Hoffmann
2022-01-17 15:05 ` Thomas Zimmermann
2022-01-17 16:05 ` Helge Deller
2022-01-17 14:53 ` Thomas Zimmermann
2022-01-18 6:11 ` Gerd Hoffmann
2022-01-18 8:09 ` Helge Deller
2022-01-17 15:00 ` Daniel Vetter
2022-01-17 15:42 ` Helge Deller
2022-01-17 15:56 ` Daniel Vetter
2022-01-17 15:58 ` Thomas Zimmermann
2022-01-17 16:21 ` Helge Deller
2022-01-17 16:38 ` Daniel Vetter
2022-01-17 17:19 ` Helge Deller
2022-01-17 19:45 ` Helge Deller
2022-01-17 21:55 ` Ilia Mirkin
2022-01-18 11:14 ` Daniel Vetter
2022-01-18 14:14 ` Thomas Zimmermann
2022-01-17 21:40 ` Jani Nikula
2022-01-17 21:44 ` Helge Deller
2022-01-18 8:38 ` Jani Nikula [this message]
2022-01-18 8:41 ` Geert Uytterhoeven
2022-01-18 11:41 ` Daniel Vetter
2022-01-18 12:11 ` Simon Ser
2022-01-18 8:54 ` Helge Deller
2022-01-18 9:33 ` Javier Martinez Canillas
2022-01-18 9:45 ` Geert Uytterhoeven
2022-01-18 11:18 ` Daniel Vetter
2022-01-18 11:42 ` Helge Deller
2022-01-18 8:41 ` 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 9:53 ` Gerd Hoffmann
2022-01-18 11:22 ` Daniel Vetter
2022-01-18 12:07 ` Gerd Hoffmann
2022-01-19 8:39 ` Pekka Paalanen
2022-01-20 9:06 ` Geert Uytterhoeven
2022-01-20 11:32 ` Daniel Vetter
2022-01-20 12:13 ` Geert Uytterhoeven
2022-01-20 12:33 ` Daniel Vetter
2022-01-20 12:46 ` Geert Uytterhoeven
2022-01-24 18:50 ` Geert Uytterhoeven
2022-01-24 19:37 ` Daniel Vetter
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 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=87a6ft5thv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--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: 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).