linux-kernel - Re: [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <57fb3864-51f1-45b4-a16a-be67e3a1451c@gmail.com>
Date: Tue, 6 May 2025 17:29:57 +0300
From: Matti Vaittinen <mazziesaccount@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Lee Jones <lee@...nel.org>,
 Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Immutable branch between MFD and Regulator due for the
 v6.16 merge window

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@...nel.org) kirjoitti:
> 
>>>> are available in the Git repository at:
> 
>>>>    ssh://git@...olite.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@...olite,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