mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee@kernel.org>,
	Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window
Date: Tue, 6 May 2025 17:29:57 +0300	[thread overview]
Message-ID: <57fb3864-51f1-45b4-a16a-be67e3a1451c@gmail.com> (raw)
In-Reply-To: <aBoYYrfANv8QLfWA@finisterre.sirena.org.uk>

On 06/05/2025 17:10, Mark Brown wrote:
> On Tue, May 06, 2025 at 08:28:33AM +0300, Matti Vaittinen wrote:
>> la 3.5.2025 klo 2.25 Mark Brown (broonie@kernel.org) kirjoitti:
> 
>>>> are available in the Git repository at:
> 
>>>>    ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/ib-mfd-regulator-v6.16
> 
>>> You need to specify a separate url and pushurl for the git remote so git
>>> generates PRs with a public URL people can use.
> 
>> I didn't spot this in regulator/for-next. Is the URL sorted? I'd love
>> to see this merged...
> 
> I've not seen any updates, you can infer the URL by hand if needed:
> 
>     s,ssh://git@gitolite,https://git,
> 
> should do it so
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/ib-mfd-regulator-v6.16
> 
> I generally don't actually pull these unless there's a dependency
> materialises, especially if I'd have to fight with my tooling for pull
> requests a bit.  If you've got a dependency then send it and mention the
> dependency in your cover letter.

Thanks for the explanation Mark. There should be no dependencies I'm 
aware of. I just assumed you'd pull it from MFD to regulator to catch 
any potential conflicts early.

It's all good for me for as long as the series gets to the rc1. I just, 
for some reason, thought that these changes are required to go via the 
regulator tree.

Sorry for the noise.

Yours,
	-- Matti

  reply	other threads:[~2025-05-06 14:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  8:40 [PATCH v3 00/14] Support ROHM Scalable PMIC family Matti Vaittinen
2025-04-08  8:40 ` [PATCH v3 01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC Matti Vaittinen
2025-04-08 16:16   ` Conor Dooley
2025-04-09  4:30     ` Matti Vaittinen
2025-04-09  5:43       ` Matti Vaittinen
2025-04-08  8:40 ` [PATCH v3 02/14] dt-bindings: mfd: " Matti Vaittinen
2025-04-08 16:11   ` Conor Dooley
2025-04-08  8:41 ` [PATCH v3 03/14] dt-bindings: mfd: bd96801: Add ROHM BD96805 Matti Vaittinen
2025-04-08  8:44 ` [PATCH v3 04/14] dt-bindings: mfd: bd96802: Add ROHM BD96806 Matti Vaittinen
2025-04-08 16:09   ` Conor Dooley
2025-04-08  8:44 ` [PATCH v3 05/14] mfd: rohm-bd96801: Add chip info Matti Vaittinen
2025-04-08  8:45 ` [PATCH v3 06/14] mfd: bd96801: Drop IC name from the regulator IRQ resources Matti Vaittinen
2025-04-08  8:45 ` [PATCH v3 07/14] regulator: bd96801: Drop IC name from the " Matti Vaittinen
2025-04-08 20:19   ` Mark Brown
2025-04-08  8:45 ` [PATCH v3 08/14] mfd: rohm-bd96801: Support ROHM BD96802 Matti Vaittinen
2025-04-08  8:46 ` [PATCH v3 09/14] regulator: bd96801: " Matti Vaittinen
2025-04-08 20:19   ` Mark Brown
2025-04-08  8:46 ` [PATCH v3 10/14] mfd: bd96801: Support ROHM BD96805 Matti Vaittinen
2025-04-08  8:46 ` [PATCH v3 11/14] regulator: bd96801: Support ROHM BD96805 PMIC Matti Vaittinen
2025-04-08  8:47 ` [PATCH v3 12/14] mfd: bd96801: Support ROHM BD96806 Matti Vaittinen
2025-04-08  8:47 ` [PATCH v3 13/14] regulator: bd96801: Support ROHM BD96806 PMIC Matti Vaittinen
2025-04-08  8:47 ` [PATCH v3 14/14] MAINTAINERS: Add BD96802 specific header Matti Vaittinen
2025-04-10  7:58 ` [PATCH v3 00/14] Support ROHM Scalable PMIC family Lee Jones
2025-04-10  8:12   ` Matti Vaittinen
2025-04-24 13:58 ` Lee Jones
2025-04-24 13:59   ` Lee Jones
2025-05-02  7:47 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window Lee Jones
2025-05-02 23:25   ` Mark Brown
2025-05-06  5:28     ` Matti Vaittinen
2025-05-06 14:10       ` Mark Brown
2025-05-06 14:29         ` Matti Vaittinen [this message]
2025-05-07 10:33     ` Lee Jones
2025-05-07 10:36       ` Lee Jones
2025-05-15 14:16 [PATCH v9 0/8] mfd: bcm590xx: Add support for BCM59054 Artur Weber
2025-05-22 14:45 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window Lee Jones

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=57fb3864-51f1-45b4-a16a-be67e3a1451c@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=robh@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®