[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8b77befd-7d45-4f54-a651-33027b46e465@sirena.org.uk>
Date: Fri, 18 Jul 2025 15:33:27 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee@...nel.org>
Cc: Michael Walle <mwalle@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Walleij <linus.walleij@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Julien Panis <jpanis@...libre.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [GIT PULL] Immutable branch between MFD, Misc and Pinctrl due
for the v6.17 merge window
On Fri, Jul 18, 2025 at 02:38:46PM +0100, Lee Jones wrote:
> For the past decade or so I've been taking cross-subsystem patch-sets
> and submitting pull-requests to all other maintainers, after testing of
> course. However, more recently you have become increasingly vocal in
> terms of an alternative approach, whereby I apply the set without
> patches that pertain to your AoR (usually Regulators) and submit an
> immutable branch for you to pull from. I have attempted both recently
> and each has received criticism, showing preference for the other.
> Honestly, I don't mind which strategy we put into place. Let's just
> agree on one and go with it.
What I'm expecting is that if I've reviewed/acked something then it'd be
applied but that if the MFD stuff is good to go then that gets applied
as is and any remaining patches get handled separately.
This was a weird case where I'd reviewed the patches without realising
there were dependencies, and those deps weren't an issue whenever
someone sent a ping.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists