[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwzerCnjvTKsEyIi@sirena.org.uk>
Date: Mon, 29 Aug 2022 16:43:40 +0100
From: Mark Brown <broonie@...nel.org>
To: Christian Kohlschütter
<christian@...lschutter.com>
Cc: m.szyprowski@...sung.com, heiko@...ech.de, lgirdwood@...il.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org, linux-rockchip@...ts.infradead.org,
m.reichl@...etechno.de, robin.murphy@....com,
vincent.legoll@...il.com, wens@...nel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to
prevent double-init
On Thu, Aug 25, 2022 at 09:28:42PM +0000, Christian Kohlschütter wrote:
> Previously, an unresolved regulator supply reference upon calling
> regulator_register on an always-on or boot-on regulator caused
> set_machine_constraints to be called twice.
Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code. Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice to only change pubished git commits if
absolutely essential.
Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists