linux-kernel - Re: [PATCH 1/2] dt_bindings: bd9576: fix regulator binfdings dt node names

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: <160192046344.23248.15447268991853037169.b4-ty@kernel.org>
Date:   Mon, 05 Oct 2020 18:54:23 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        mazziesaccount@...il.com
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-power@...rohmeurope.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt_bindings: bd9576: fix regulator binfdings dt node names

On Mon, 5 Oct 2020 11:18:19 +0300, Matti Vaittinen wrote:
> Add regulator- prefix to allowed regulator node names. Prefix is expected
> by the driver and the actual binding yaml description.

Applied to

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

Thanks!

[1/2] regulator: bd9576: fix regulator binfdings dt node names
      commit: f2deb05688c25ac124a7e33bc15b1ab13d7fb1a7
[2/2] regulator: bd9576: Fix print
      commit: 184cdb8f6d391b379bb768b0c203600f5657176b

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