From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93E85C43217 for ; Thu, 1 Dec 2022 10:42:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229667AbiLAKmX (ORCPT ); Thu, 1 Dec 2022 05:42:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50334 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230175AbiLAKmR (ORCPT ); Thu, 1 Dec 2022 05:42:17 -0500 Received: from gandalf.ozlabs.org (gandalf.ozlabs.org [150.107.74.76]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3222F9F4AC; Thu, 1 Dec 2022 02:42:16 -0800 (PST) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4NNCLc4QCXz4xFy; Thu, 1 Dec 2022 21:42:00 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellerman.id.au; s=201909; t=1669891334; bh=4hif7EODqPU9RIQoNSM7f4kViT96m8PqRMy1FOSRqmw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=XMDViV6CFDY+O8nTTE8IlEWWvY7H8YPqwD0Tn3KS84kUAblouGGNC2+Nia8sW2MYv qiQITUGJnoNf2rF8FqcIgIFTtKJlyIpcKBWiNrEakO5NLQ+ickTPEjtr01+GlyanLx mzZ9YX/t1jp5UON6rpZmvdKzHLeuceJXW2c99G//FjEB6EQyCPN8TlRw5ClPGntYn1 1lstUDxUIwXt5rogz0qwgKe9XH3/+5CPLNT6DZ3ksaq4/yXNeIe6xOWsdnc3/9h44G yfuCxdwdv4chZHzuDDmEcJxiTEJT36pr3DPrHlRrFjnXSjff4fqmP4a9zPs8OfNA43 pIMyXosyZ93DA== From: Michael Ellerman To: =?utf-8?B?QXLEsW7DpyDDnE5BTA==?= , Andrew Lunn Cc: Vladimir Oltean , Krzysztof Kozlowski , soc@kernel.org, "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Gregory Clement , Sebastian Hesselbarth , Russell King , Nicolas Ferre , Alexandre Belloni , Claudiu Beznea , Ray Jui , Scott Branden , Broadcom internal kernel review list , Florian Fainelli , Hauke Mehrtens , =?utf-8?Q?Rafa?= =?utf-8?Q?=C5=82_Mi=C5=82ecki?= , Hans Ulli Kroll , Linus Walleij , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Matthias Brugger , Andy Gross , Bjorn Andersson , Konrad Dybcio , Geert Uytterhoeven , Magnus Damm , Maxime Coquelin , Alexandre Torgue , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Stefan Agner , Heiko Stuebner , Thomas Bogendoerfer , Sergio Paracuellos , Nicholas Piggin , Christophe Leroy , Tim Harvey , Peng Fan , Rasmus Villemoes , Frank Wunderlich , Michael Riesch , Oleksij Rempel , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-sunxi@lists.linux.dev, linux-rockchip@lists.infradead.org, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH 0/5] remove label = "cpu" from DSA dt-binding In-Reply-To: <32638470-b074-3b14-bfb2-10b49307b9e3@arinc9.com> References: <20221130141040.32447-1-arinc.unal@arinc9.com> <32638470-b074-3b14-bfb2-10b49307b9e3@arinc9.com> Date: Thu, 01 Dec 2022 21:42:00 +1100 Message-ID: <877czbs8w7.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ar=C4=B1n=C3=A7 =C3=9CNAL writes: > On 30.11.2022 18:55, Andrew Lunn wrote: >> On Wed, Nov 30, 2022 at 05:10:35PM +0300, Ar=C4=B1n=C3=A7 =C3=9CNAL wrot= e: >>> Hello folks, >>> >>> With this patch series, we're completely getting rid of 'label =3D "cpu= ";' >>> which is not used by the DSA dt-binding at all. >>> >>> Information for taking the patches for maintainers: >>> Patch 1: netdev maintainers (based off netdev/net-next.git main) >>> Patch 2-3: SoC maintainers (based off soc/soc.git soc/dt) >>> Patch 4: MIPS maintainers (based off mips/linux.git mips-next) >>> Patch 5: PowerPC maintainers (based off powerpc/linux.git next-test) >>=20 >> Hi Ar=C4=B1n=C3=A7 >>=20 >> So your plan is that each architecture maintainer merges one patch? > > Initially, I sent this series to soc@kernel.org to take it all but Rob=20 > said it must be this way instead. > >>=20 >> That is fine, but it is good to be explicit, otherwise patches will >> fall through the cracks because nobody picks them up. I generally use >> To: to indicate who i expect to merge a patch, and everybody else in >> the Cc: > > Thanks for this, I'll follow suit if I don't see any activity for a few=20 > weeks. IMHO the best solution if the patches are truly independent is to send them independantly to each maintainer. That way there's no confusion about whether someone else will take the series. It's also simpler for maintainers to apply a single standalone patch vs pick a single patch from a larger series. cheers