Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     Martin Fuzzey <martin.fuzzey@flowbird.group>
Cc:     Support Opensource <support.opensource@diasemi.com>,
        Adam Ward <DLG-Adam.Ward.opensource@dm.renesas.com>,
        Benjamin Bara <benjamin.bara@skidata.com>,
        linux-kernel@vger.kernel.org
In-Reply-To: <20230804083514.1887124-1-martin.fuzzey@flowbird.group>
References: <20230804083514.1887124-1-martin.fuzzey@flowbird.group>
Subject: Re: [PATCH] regulator: da9063: better fix null deref with partial
 DT
Message-Id: <169116752497.109025.2270208458219621904.b4-ty@kernel.org>
Date:   Fri, 04 Aug 2023 17:45:24 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 04 Aug 2023 10:34:30 +0200, Martin Fuzzey wrote:
> Two versions of the original patch were sent but V1 was merged instead
> of V2 due to a mistake.
> 
> So update to V2.
> 
> The advantage of V2 is that it completely avoids dereferencing the pointer,
> even just to take the address, which may fix problems with some compilers.
> Both versions work on my gcc 9.4 but use the safer one.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: da9063: better fix null deref with partial DT
      commit: 30c694fd4a99fbbc4115d180156ca01b60953371

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark