All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Alex Elder <elder@riscstar.com>,
	lgirdwood@gmail.com, alexandre.belloni@bootlin.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	mat.jonczyk@o2.pl, dlan@gentoo.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux.amoon@gmail.com, troymitchell988@gmail.com,
	guodong@riscstar.com, linux-rtc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v13 0/7] spacemit: introduce P1 PMIC support
Date: Tue, 16 Sep 2025 13:27:24 +0100	[thread overview]
Message-ID: <20250916122724.GB3585920@google.com> (raw)
In-Reply-To: <c8bcfff9-9d2a-426d-9df8-100efd2af64f@sirena.org.uk>

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 [李琼斯]

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Alex Elder <elder@riscstar.com>,
	lgirdwood@gmail.com, alexandre.belloni@bootlin.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	mat.jonczyk@o2.pl, dlan@gentoo.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux.amoon@gmail.com, troymitchell988@gmail.com,
	guodong@riscstar.com, linux-rtc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v13 0/7] spacemit: introduce P1 PMIC support
Date: Tue, 16 Sep 2025 13:27:24 +0100	[thread overview]
Message-ID: <20250916122724.GB3585920@google.com> (raw)
In-Reply-To: <c8bcfff9-9d2a-426d-9df8-100efd2af64f@sirena.org.uk>

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 [李琼斯]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-09-16 12:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 17:20 [PATCH v13 0/7] spacemit: introduce P1 PMIC support Alex Elder
2025-08-25 17:20 ` Alex Elder
2025-08-25 17:20 ` [PATCH v13 1/7] dt-bindings: mfd: add support the SpacemiT P1 PMIC Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-08-25 17:20 ` [PATCH v13 2/7] mfd: simple-mfd-i2c: add SpacemiT P1 support Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-08-29 11:03   ` kernel test robot
2025-08-29 11:03     ` kernel test robot
2025-08-25 17:20 ` [PATCH v13 3/7] regulator: spacemit: support SpacemiT P1 regulators Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-08-25 17:20 ` [PATCH v13 4/7] rtc: spacemit: support the SpacemiT P1 RTC Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-09-16 14:57   ` (subset) " Alexandre Belloni
2025-09-16 14:57     ` Alexandre Belloni
2025-08-25 17:20 ` [PATCH v13 5/7] riscv: dts: spacemit: enable the i2c8 adapter Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-08-25 17:20 ` [PATCH v13 6/7] riscv: dts: spacemit: define fixed regulators Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-08-25 17:20 ` [PATCH v13 7/7] riscv: dts: spacemit: define regulator constraints Alex Elder
2025-08-25 17:20   ` Alex Elder
2025-09-03 12:19 ` (subset) [PATCH v13 0/7] spacemit: introduce P1 PMIC support Lee Jones
2025-09-11 16:36   ` Alex Elder
2025-09-11 16:36     ` Alex Elder
2025-09-11 18:57     ` Mark Brown
2025-09-11 18:57       ` Mark Brown
2025-09-16  8:42       ` Lee Jones
2025-09-16  8:42         ` Lee Jones
2025-09-16 11:50         ` Mark Brown
2025-09-16 11:50           ` Mark Brown
2025-09-16 12:27           ` Lee Jones [this message]
2025-09-16 12:27             ` Lee Jones
2025-09-16 13:05             ` Yixun Lan
2025-09-16 13:05               ` Yixun Lan
2025-09-11 19:55     ` Yixun Lan
2025-09-11 19:55       ` Yixun Lan
2025-09-16 21:54 ` Mark Brown
2025-09-16 21:54   ` Mark Brown
2025-10-14  0:01 ` Yixun Lan
2025-10-14  0:01   ` Yixun Lan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250916122724.GB3585920@google.com \
    --to=lee@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=alexandre.belloni@bootlin.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=elder@riscstar.com \
    --cc=guodong@riscstar.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux.amoon@gmail.com \
    --cc=mat.jonczyk@o2.pl \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    --cc=troymitchell988@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.