[PATCH v8 4/9] mfd: bcm590xx: Add support for multiple device types + BCM59054 compatible

[Mark Brown]

On Thu, May 15, 2025 at 08:13:57AM +0100, Lee Jones wrote:
> On Wed, 14 May 2025, Mark Brown wrote:

> > Could you be more explicit what you're looking for here, the diffstat is
> > entirely MFD?

> Okay, more explicitly, I can merge this and MFD will have no issue.
> However, the Regulator commits make use of 'pmu_id' introduced in this
> change and would therefore cause a compile break.  So we could:

>   1. Apply this now and merge the dependents next cycle
>   2. Apply this now and provide an IB
>   3. Wait for all Acks and apply as a unified set

> We usually choose 3, hence my assumptions above.

Well, you choose 3 - I do think it'd be a lot easier to go with option
2, or with applying the rest to your tree as acks come in.  There seemed
to still be a reasonable amount of discussion on the MFD bits (eg,
there's some formatting comments still) so I was expecting this series
to churn some more and was waiting for a resend.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20250515/4e42f316/attachment.sig>