[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250916084229.GG1637058@google.com>
Date: Tue, 16 Sep 2025 09:42:29 +0100
From: Lee Jones <lee@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Alex Elder <elder@...cstar.com>, lgirdwood@...il.com,
alexandre.belloni@...tlin.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, mat.jonczyk@...pl, dlan@...too.org,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
alex@...ti.fr, linux.amoon@...il.com, troymitchell988@...il.com,
guodong@...cstar.com, linux-rtc@...r.kernel.org,
devicetree@...r.kernel.org, linux-riscv@...ts.infradead.org,
spacemit@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v13 0/7] spacemit: introduce P1 PMIC support
On Thu, 11 Sep 2025, Mark Brown wrote:
> On Thu, Sep 11, 2025 at 11:36:41AM -0500, Alex Elder wrote:
>
> > That leaves patch 3, which enables regulator support, and patch
> > 4, which adds RTC support.
>
> > How should these two patches be merged? Mark has reviewed the
> > regulator patch 3 and Alexandre has acked the RTC patch 4.
>
> We'd both have been expecting them to go via MFD.
Why? I don't see any dependencies between them (usually a shared MFD
header-file). If there are no deps, it should be taken through its own
repo, no?
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists