linux-kernel - Re: [PATCH] regulator: rtmv20: Update DT binding document and property name parsing

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: <160146714296.40216.643020252480635401.b4-ty@kernel.org>
Date:   Wed, 30 Sep 2020 12:59:08 +0100
From:   Mark Brown <broonie@...nel.org>
To:     cy_huang <u0084500@...il.com>, robh+dt@...nel.org
Cc:     lgirdwood@...il.com, cy_huang@...htek.com,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] regulator: rtmv20: Update DT binding document and property name parsing

On Wed, 30 Sep 2020 18:08:00 +0800, cy_huang wrote:
> 1. Add vendor suffix to all proprietary properties.
> 2. Fix typo.
> 3. Change lsw to normal property, not pattern property.
> 4. Due to item 1, modify source code for property parsing.

Applied to

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

Thanks!

[1/1] regulator: rtmv20: Update DT binding document and property name parsing
      commit: 89a5f77e3f3a7fb8d6cf25668489d66069ebe4b7

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