[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBoYYrfANv8QLfWA@finisterre.sirena.org.uk>
Date: Tue, 6 May 2025 23:10:42 +0900
From: Mark Brown <broonie@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>
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 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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists