linux-kernel - Re: [PATCH v2 20/22] arm64: dts: apple: t8103: Add Apple Type-C PHY and dwc3 nodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025090726-overcoat-unskilled-3228@gregkh>
Date: Sun, 7 Sep 2025 14:51:11 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Alyssa Anne Rosenzweig <alyssa@...enzweig.io>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Sven Peter <sven@...nel.org>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, Felipe Balbi <balbi@...nel.org>,
	Janne Grunau <j@...nau.net>, Neal Gompa <neal@...pa.dev>,
	Vinod Koul <vkoul@...nel.org>,
	Kishon Vijay Abraham I <kishon@...nel.org>,
	Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	Philipp Zabel <p.zabel@...gutronix.de>, Frank Li <Frank.Li@....com>,
	Ran Wang <ran.wang_1@....com>, Peter Chen <peter.chen@....com>,
	linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, asahi@...ts.linux.dev,
	linux-arm-kernel@...ts.infradead.org, linux-phy@...ts.infradead.org,
	Hector Martin <marcan@...can.st>
Subject: Re: [PATCH v2 20/22] arm64: dts: apple: t8103: Add Apple Type-C PHY
 and dwc3 nodes

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