[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250916122724.GB3585920@google.com>
Date: Tue, 16 Sep 2025 13:27:24 +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 Tue, 16 Sep 2025, Mark Brown wrote:
> On Tue, Sep 16, 2025 at 09:42:29AM +0100, Lee Jones wrote:
> > On Thu, 11 Sep 2025, Mark Brown wrote:
> > > On Thu, Sep 11, 2025 at 11:36:41AM -0500, Alex Elder wrote:
>
> > > > 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?
>
> I used to just apply things but at some point Linus complained about
> cases where the MFD ended up not getting merged (missing the merge
> window or whatever) so I've been treating them like they had an actual
> dependency.
Not sure I've seen any of that from Linus, but I don't doubt you. The
MFD part has been merged now, so it's save to go ahead and apply the
Regulator part.
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists