linux-kernel - Re: [PATCH v2 0/2] regulator: Add driver for Maxim MAX20086-MAX20089

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] [day] [month] [year] [list]

Message-Id: <164156599462.2077470.16513079176958565691.b4-ty@kernel.org>
Date:   Fri, 07 Jan 2022 14:33:14 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
        linux-kernel@...r.kernel.org
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Watson Chow <watson.chow@...et.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH v2 0/2] regulator: Add driver for Maxim MAX20086-MAX20089

On Fri, 7 Jan 2022 00:43:48 +0200, Laurent Pinchart wrote:
> From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> 
> Hello,
> 
> This small series adds a new driver (along with DT bindings) for the
> Maxim MAX20086-MAX20089 camera power protectors.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulators: Add bindings for Maxim MAX20086-MAX20089
      commit: 764aaa4e031a9acd26babc622cabe652f57bbb04
[2/2] regulator: Add MAX20086-MAX20089 driver
      commit: bfff546aae50ae68ed395bf0e0848188d27b0ba3

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