Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp5400641pxb; Wed, 19 Jan 2022 18:09:50 -0800 (PST) X-Google-Smtp-Source: ABdhPJxvSukWIY3Wu0Mq2EOonzdOIImpF7SUN8XD1oSKm3c4Dqbsg8vjXn9VBvJm6m4s/TYmmYHd X-Received: by 2002:a17:90b:4c50:: with SMTP id np16mr7903431pjb.51.1642644589894; Wed, 19 Jan 2022 18:09:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642644589; cv=none; d=google.com; s=arc-20160816; b=dcCpkba3IV9WbiYJKDmOjFkMhciQRDPetrT0E9DoA55NpLxr/I64ZDYyWcFaoAZAWc wEhpQpU5vVpFlTGOpCecjAN1GcEOzeWAqTGg2g7i3BJcAUu+ZgXq1la8ZNBKeBZ27W3Z djh5qEDrV4O0PiMKKZxWp4V7YE9AlnKYHK1Be2wmBjUmWLcGhNOsDJk3Yp0+9gLwT7dw LmZP2I9VriiRJL8FH3siyZfcyKqPurzfnaKvg+0bfSX8MKK2iLLBa4z2MNq2yuVJl+Cz GBaj2sGBEhUIiZI676cLPpbLWiHGwg1tk9MugKQ3ZBGDJg3cjETCoVjPhgnCcTPt4wKv BN4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=uRFhx0l+e0ed4wS3RUIFPjxFMaQUtU4eks+w7Sri8W8=; b=mGjXXQTsmVPZAus5ni0o/Z4VH/DuE7ZNmEXfaVZGjBigRuDioMLKlVUM6SNvZDP2fJ X4ktuTnSbGBLaMvxUupVrwEf2oDCOz0qJbxaPK4kPrMjXdTPeXTuwxTuHh2LsILAprwf TLPMpCrMgHkg1BsWou0VoyidjN763UdMFdOqt7OwcbIMYZe9DHW/BDCFRWatdIIoHyyO CxIe1hMc/4vpYuKfEsitLkzGVlwnNfTHPO0utyJ74f7p82hKdY2oY+BRsMj5+6Ro/T54 aKl3e8zubCAnhuym1Ru9c6OrD1JGs4i1WK7ojUb8meBDmrIUp2ydzeeAnBBiaE3IqxBb I+uw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l10si1581108pfu.243.2022.01.19.18.09.13; Wed, 19 Jan 2022 18:09:49 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233212AbiARJpP (ORCPT + 99 others); Tue, 18 Jan 2022 04:45:15 -0500 Received: from mail-ua1-f53.google.com ([209.85.222.53]:33503 "EHLO mail-ua1-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229620AbiARJpO (ORCPT ); Tue, 18 Jan 2022 04:45:14 -0500 Received: by mail-ua1-f53.google.com with SMTP id u6so35522187uaq.0; Tue, 18 Jan 2022 01:45:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uRFhx0l+e0ed4wS3RUIFPjxFMaQUtU4eks+w7Sri8W8=; b=MNKFQ4bVp34xzc4RxSRvXhDFAlw8i4o3hgln/fQvY3AB2CMVo6zcIN6dpl48sA4K5R 5MVoqunP9Ijc2WnmcZkG6BZKjCXnbNLIYd+fORqcACJMud67nYuo1GHqIyCJzkL1jcNP OxDYvGCHond0QpsvEegy17bWr8a0vRZpn9qdb+PUqcM8whBoAJLBsjc+QSgNkHoG9WNE vUfOqD4tZeJb4O0/e+b+XOl4QxtjejXtgh+wX2KqG8S1Taq0Zk3mtOtjyyI5pR5pMinr y9AaNzNKEO8uur1z+oyrAXwo/D2QpuUFtkkQkdg22BEJfg7Dzd/IYZqhz6PXCfdmu+Y3 +3bg== X-Gm-Message-State: AOAM530BS2A9b1hpi08xFIPJq9Azf+pueov+O2AhHEQcA0dxZBrvoHX1 2BBTunj6EPaq6EdQ0Snw3dQ1waOTUaftuA== X-Received: by 2002:ab0:4e17:: with SMTP id g23mr9431553uah.24.1642499112913; Tue, 18 Jan 2022 01:45:12 -0800 (PST) Received: from mail-vk1-f174.google.com (mail-vk1-f174.google.com. [209.85.221.174]) by smtp.gmail.com with ESMTPSA id q28sm4064433vsl.2.2022.01.18.01.45.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Jan 2022 01:45:12 -0800 (PST) Received: by mail-vk1-f174.google.com with SMTP id bj47so12022117vkb.13; Tue, 18 Jan 2022 01:45:11 -0800 (PST) X-Received: by 2002:a1f:384b:: with SMTP id f72mr9456081vka.0.1642499111709; Tue, 18 Jan 2022 01:45:11 -0800 (PST) MIME-Version: 1.0 References: <97d49bca-f5f7-dba4-b62d-b6fcdd4276ac@suse.de> <87ee5659dt.fsf@intel.com> <4f1d6018-d74e-8e62-ea4d-0ca79c6bbbc5@gmx.de> <87a6ft5thv.fsf@intel.com> <5ba33e10-7d75-9f9a-dfd6-c04608d230a4@gmx.de> <4f65fdd9-4b73-ca83-cf6e-c60c7ccd6558@redhat.com> In-Reply-To: <4f65fdd9-4b73-ca83-cf6e-c60c7ccd6558@redhat.com> From: Geert Uytterhoeven Date: Tue, 18 Jan 2022 10:45:00 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] MAINTAINERS: Add Helge as fbdev maintainer To: Javier Martinez Canillas Cc: Helge Deller , Jani Nikula , Thomas Zimmermann , Daniel Vetter , Linux Fbdev development list , Linus Torvalds , Linux Kernel Mailing List , DRI Development Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Javier, On Tue, Jan 18, 2022 at 10:33 AM Javier Martinez Canillas 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 wrote: > >>> On 1/17/22 22:40, Jani Nikula wrote: > >>>> On Mon, 17 Jan 2022, Thomas Zimmermann 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