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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7223BCAC581 for ; Sun, 7 Sep 2025 12:54:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=X576HBP8IjKTItNo7fxh5MkRv+h6NrGf2e9T57DHT4Y=; b=gAoh7sF8mhHPRQxXwSDbOS1LSt rba4FM9eesXWmD3NMJ87gp22kI3/aRpnbCxr4yev8A+C5vaLJUPt9wQhC21LvA3YVgNGTsSnNP+7u wCT5mSuiOnu3hmNhyi0G8rupw149snmaymNu5wVDT2xw0IBFCcgOjBCJQ6bcQ9b19Gcp5HnI48EBc 5A50c1Jaz45UazxVZC3HQ+qO+Uz99YWMDk4e1KFrbWmoPe2xos/E2L6Qijl/M827ZihGQoxNCifnJ 0mbOO1luksFX3HPFBSLWzgxConllhXbOhZFk2ThHSqSjgQy88NQ26DN0br7jpGLX5mP8RRmltJCuE 2uqErBTA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1uvEuK-0000000B9zW-3UlW; Sun, 07 Sep 2025 12:54:12 +0000 Received: from sea.source.kernel.org ([172.234.252.31]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1uvErU-0000000B9Ff-3pBP; Sun, 07 Sep 2025 12:51:19 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id 749C840518; Sun, 7 Sep 2025 12:51:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BB9B1C4CEF0; Sun, 7 Sep 2025 12:51:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1757249474; bh=IWYocY3Q/qyYFd0mqeYzdKytf2h0IHxXtx9zAXWQ5sM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=d4kJMwi2GGoks7Kj/YqNlzkZ8fzdRPWDzA8Yye8QtWHeG0O4qtLYiLNvDGGw9/ETt hxpApDrcdwzYed/fwOJs1CKTfPyOtqsQcv0lY+HwPhbbmsS5JoC+iPcb2PrTS2Q24Q OLHeb2bfAj7QKuRymS01IPveabspeYWifp1uRcEA= Date: Sun, 7 Sep 2025 14:51:11 +0200 From: Greg Kroah-Hartman To: Alyssa Anne Rosenzweig Cc: Krzysztof Kozlowski , Sven Peter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Felipe Balbi , Janne Grunau , Neal Gompa , Vinod Koul , Kishon Vijay Abraham I , Thinh Nguyen , Heikki Krogerus , Philipp Zabel , Frank Li , Ran Wang , Peter Chen , linux-usb@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-phy@lists.infradead.org, Hector Martin Subject: Re: [PATCH v2 20/22] arm64: dts: apple: t8103: Add Apple Type-C PHY and dwc3 nodes Message-ID: <2025090726-overcoat-unskilled-3228@gregkh> References: <20250906-atcphy-6-17-v2-0-52c348623ef6@kernel.org> <20250906-atcphy-6-17-v2-20-52c348623ef6@kernel.org> <20250907-zippy-auburn-koel-d6da32@kuoka> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250907_055117_350531_EB38386A X-CRM114-Status: GOOD ( 17.43 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sun, Sep 07, 2025 at 08:43:32AM -0400, Alyssa Anne Rosenzweig wrote: > > Please do not combine DTS patches in patchsets for Greg (e.g. USB). Greg > > expressed that many times, that he takes all or nothing, and DTS cannot > > go via driver branches/trees. > > >From the cover letter, emphasis mine: > > > With the dwc3 glue driver this series can now also be merged independently > > once it's ready: Patches 1-4 can go through the dwc3 tree, 5-15 through > > tipd, 16-18 should go together through the phy tree, and I'll take the > > DTS changes through my tree. **If everyone's happy with the overall > > approach here I can also just send these as individual series** > That's great, but a major pain in the butt for any maintainer. It would require me to manually pick out the patches to be added to my tree and manually apply them? We have good tools now, b4, that wants to take a whole patch series. And you want me to take a whole patch series, as I can now add the info that is in 00/XX to the "merge point" of a big patch series to preserve the information that is provided here. So you loose out if you that is not preserved in the tree, and you make more work for maintainers to try to sift through just what should, and should not, be taken. Remember, some of us maintainers get 1000+ emails a day to do something with. Our development process is optimized for our most limited resource, maintainers, not developers, sorry. Think about it if you were on the receiving end of this, what would you want to see present for you to be able to review and then apply this to your tree? So please, split patches up into "one series per tree". It's the only sane way for us to work. Yes, it's a pain for platform/dts stuff at times, but for everything else, it works really well. thanks, greg k-h