[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250515131321.GG2936510@google.com>
Date: Thu, 15 May 2025 14:13:21 +0100
From: Lee Jones <lee@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Artur Weber <aweber.kernel@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Ray Jui <rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
Stanislav Jakubek <stano.jakubek@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH v8 4/9] mfd: bcm590xx: Add support for multiple device
types + BCM59054 compatible
On Thu, 15 May 2025, Mark Brown wrote:
> On Thu, May 15, 2025 at 01:28:15PM +0200, Artur Weber wrote:
> > On 5/15/25 11:33, Mark Brown wrote:
> > > On Thu, May 15, 2025 at 10:20:00AM +0100, Lee Jones wrote:
>
> > > > I can go with 2 in this case. Applying in dribs-and-drabs as Acks come
> > > > in would be sub-optimal and would likely end up in a mess.
>
> > > Well, then just going a head and applying them on a branch with a tag
> > > seems easier than delaying then.
>
> > I can split the patchset into two parts (one for MFD, one for regulator)
> > if it helps.
>
> There's still a dependency on the MFD bits whatever happens.
Right. That won't help since you need to describe the deps. Submitting
them as a set was the correct thing to do.
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists