linux-kernel - Re: [PATCH] regulator: max77826: Remove erroneous additionalProperties

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: <158799504950.16924.8566981464657105053.b4-ty@kernel.org>
Date:   Mon, 27 Apr 2020 14:44:09 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Iskren Chernev <iskren.chernev@...il.com>,
        Rob Herring <robh+dt@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-arm-msm@...r.kernel.org, Andy Gross <agross@...nel.org>,
        devicetree@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH] regulator: max77826: Remove erroneous additionalProperties

On Sat, 25 Apr 2020 15:53:35 +0300, Iskren Chernev wrote:
> In this particular location additionalProperties actually declares a property
> named `additionalProperties` instead of specifying there should be no other
> properties.
> 
> Signed-off-by: Iskren Chernev <iskren.chernev@...il.com>
> ---
> Fix bindings documentation for max77826 regulator as discussed in
> https://lore.kernel.org/lkml/20200413164440.1138178-1-iskren.chernev@gmail.com/T/#m9e9904560e68bcd98980fa0e68fe190525033af6
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: max77826: Remove erroneous additionalProperties
      commit: 48dd1a7938e37d6d6414a20266394f858b37f10a

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