Received: by 2002:a05:6a10:8a4d:0:0:0:0 with SMTP id dn13csp81642pxb; Thu, 12 Aug 2021 11:14:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdC6n/Mtmg+gS2QdGs5+OMKLmpB+x38kuSPU1bVtkP0dN4fKSJwN3rtCNI4DMAwc8QYqsW X-Received: by 2002:a17:906:c087:: with SMTP id f7mr4820670ejz.487.1628792091759; Thu, 12 Aug 2021 11:14:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628792091; cv=none; d=google.com; s=arc-20160816; b=L+mXKVEbWHPrfKnSkBOVBCCt3AreInjM80D8LrJYUXBtB2r8nE9EZ8GdcMHntKrizR xE8vPWBDJ3nRVSdO4imdLi2T4uTJAhBOwi3SYTGun83bSWHpOGPX9lfMvxu3BIcuGJgY pBjDRUoccArolP9fOzKidXkgBlYkdGIEz4n+aBHFQA0rGP9AFYx089K+xhhyfzTIDP07 98vmLA107R4YyDPqee7OjgyeSl7use60DExLtn0OEWqRozHkRNOFL4AdgwH2lWWx1DbC eyuqa+B/+MLIDhLqcoVOqIKkYkYKP9JuY7r/bbI6oNc9BvcWsbtzc0Q/SmAwNb2084Rr oChA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject :organization:from:references:cc:to:dkim-signature:dkim-signature; bh=Qi9jWdZSJj/m82RJPqM2XKkZ0Klj1CgP0gfzMHD9/qk=; b=Q4A3RESBMXLq+7NnSrpGL3LFmur7pIshlxiCZEbYpm+sK0+5uSeRwSfOIVWy+3zsRr JXX2Z4oBiHPAYqNpYF3iwBSe8dVknsynU9CTFRumSiZU0rOC16RGVypVIIub+LrVykXJ TZ1ToKC0Tppcg1KPHMlXpMjhze7Rr2CQ27kgYH+QPckFBnQaNC0dal7RTCFYRIUVZp7y S4TFNVZJ3rdxz31SAWXxvA1gY/0JeRVptM4PImySZRITQrAm9qqTQ666hwik9O9ioYb+ Unr93y1UDMW6UAxomwVbiU/BgRtnLoAh024JGuib1UrpJdLHW0+VcGD4UaWcDDNIC7Vl RXqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=YVLHPWfe; dkim=neutral (no key) header.i=@suse.de header.b=bT1Ek2Cw; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p3si3916039ejy.228.2021.08.12.11.14.27; Thu, 12 Aug 2021 11:14:51 -0700 (PDT) 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; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=YVLHPWfe; dkim=neutral (no key) header.i=@suse.de header.b=bT1Ek2Cw; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238077AbhHLPbG (ORCPT + 99 others); Thu, 12 Aug 2021 11:31:06 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:47424 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236547AbhHLPbF (ORCPT ); Thu, 12 Aug 2021 11:31:05 -0400 Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 557C91FF5B; Thu, 12 Aug 2021 15:30:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1628782239; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Qi9jWdZSJj/m82RJPqM2XKkZ0Klj1CgP0gfzMHD9/qk=; b=YVLHPWfepY5REPMwTCV+MUl5T6hDCOK33Ksvk1CGWS5eHw1Ns6hqOHfPQr0F3D3sA0ERlo uaX67Bzcp19Sl0dZAs/RfDjieMLLd2Zwi49fuyegZt2MBDOYBVNsJoybvdf16FGut457Zu PQbY8E5bjVjiu7IUklsUhv9MMIJCAJA= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1628782239; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Qi9jWdZSJj/m82RJPqM2XKkZ0Klj1CgP0gfzMHD9/qk=; b=bT1Ek2CwBp+ljIqbnci9w6AnNiyWIz806gqxJmxHQeQLYqVlmT0KpWQAJSjvbfGdjg9Mu3 M6Ah2igmp3DbqQDA== Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap1.suse-dmz.suse.de (Postfix) with ESMTPS id A52C013AC3; Thu, 12 Aug 2021 15:30:38 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap1.suse-dmz.suse.de with ESMTPSA id WMngJp4+FWF+cwAAGKfGzw (envelope-from ); Thu, 12 Aug 2021 15:30:38 +0000 To: Shawn Guo , Krzysztof Kozlowski Cc: Chester Lin , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-serial@vger.kernel.org, Greg Kroah-Hartman , Oleksij Rempel , Stefan Riedmueller , Matthias Schiffer , Li Yang , Fabio Estevam , Matteo Lisi , Frieder Schrempf , Tim Harvey , Jagan Teki , s32@nxp.com, catalin-dan.udma@nxp.com, bogdan.hamciuc@nxp.com, bogdan.folea@nxp.com, ciprianmarian.costea@nxp.com, radu-nicolae.pirea@nxp.com, ghennadi.procopciuc@nxp.com, Matthias Brugger , "Ivan T . Ivanov" , "Lee, Chun-Yi" References: <20210805065429.27485-1-clin@suse.com> <20210805065429.27485-9-clin@suse.com> <32310c2a-9800-8b04-b6ac-d8ada044c0f8@kernel.org> <20210809080346.GO30984@dragon> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Organization: SUSE Software Solutions Germany GmbH Subject: Re: [PATCH 8/8] MAINTAINERS: Add an entry for NXP S32G2 boards Message-ID: <3c65f75d-724f-a438-1e22-6baeb745a8e5@suse.de> Date: Thu, 12 Aug 2021 17:30:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: <20210809080346.GO30984@dragon> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Shawn and Krzysztof, On 09.08.21 10:03, Shawn Guo wrote: > On Thu, Aug 05, 2021 at 09:49:51AM +0200, Krzysztof Kozlowski wrote: >> On 05/08/2021 08:54, Chester Lin wrote: >>> Add a new entry for the maintenance of NXP S32G2 DT files. >>> >>> Signed-off-by: Chester Lin >>> --- >>> MAINTAINERS | 6 ++++++ >>> 1 file changed, 6 insertions(+) >>> >>> diff --git a/MAINTAINERS b/MAINTAINERS >>> index 36aee8517ab0..3c6ba6cefd8f 100644 >>> --- a/MAINTAINERS >>> +++ b/MAINTAINERS >>> @@ -2281,6 +2281,12 @@ F: arch/arm/boot/dts/nuvoton-wpcm450* >>> F: arch/arm/mach-npcm/wpcm450.c >>> F: drivers/*/*wpcm* >>> >>> +ARM/NXP S32G2 ARCHITECTURE Suggestion from NXP is to use the broader S32G name. >>> +M: Chester Lin >>> +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers) >>> +S: Maintained >>> +F: arch/arm64/boot/dts/freescale/s32g2* >> >> I support the idea of sub-sub-architecture maintainers but I think idea >> of in-file addresses was preferred: >> https://lore.kernel.org/lkml/20200830122922.3884-1-shawnguo@kernel.org/ I had specifically asked Chester to add a MAINTAINERS section. Is your apparent suggestion of not accepting this MAINTAINERS patch based on the assumption that we're dealing with only one email address in three files? What do you see as the threshold to warrant a section? From my point of view, above MAINTAINERS entry is incomplete, as we should CC the full team working on S32G for patch review, not just Chester himself. So that would in my mind have been additional R: and L: entries in that MAINTAINERS section. > Thanks for reminding that the patch didn't land. I just resent it with > your Reviewed-by tag added. Thanks! Your above patch does not make clear to me what syntax we should use for adding email addresses to .dts[i] files now: https://lore.kernel.org/lkml/20210809081033.GQ30984@dragon/ Especially when not dealing with file authors. I get the impression it is not a replacement for an F: wildcard used in MAINTAINERS, but rather a complement? Please understand that this is not about a single .dts file, as your patch suggests, but about a complete SoC family consisting of s32g*.dts* as well as in the future drivers specific to this platform. It seems way easier to specify the list of maintainers/reviewers in MAINTAINERS once with suitable wildcard paths, than copying them into each and every .dtsi and .dts file and driver .c/.h and later needing to sync multiple places. If a bot or user has fixes or cleanups for the S32G code, we want to know about it, so that NXP can consider it for their BSP branches and SUSE for our SLE branches, and obviously for follow-up patch series that are already in the works and waiting on this one. Once merged, I would expect Chester or someone from NXP to set up an S32G tree on kernel.org that gets integrated into linux-next and sends pull requests to the SoC tree maintainers without bothering i.MX and Layerscape maintainers. Did you handle that differently for S32V? Thanks, Andreas P.S. Have you checked or considered whether your script change might start to CC non-existing email addresses, since we wouldn't be allowed to remove them from copyright or authorship statements to prevent that? -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)