linux-kernel - Re: [PATCH] dt-bindings: regulator: pca9450: Remove restrictions for regulator-name

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: <165947208205.2174956.10539628877269191065.b4-ty@kernel.org>
Date:   Tue, 02 Aug 2022 21:28:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Frieder Schrempf <frieder@...s.de>,
        linux-kernel@...r.kernel.org, Robin Gong <yibin.gong@....com>,
        devicetree@...r.kernel.org
Cc:     Rob Herring <robh@...nel.org>, Per-Daniel Olsson <perdo@...s.com>,
        Frieder Schrempf <frieder.schrempf@...tron.de>,
        Rickard x Andersson <rickaran@...s.com>
Subject: Re: [PATCH] dt-bindings: regulator: pca9450: Remove restrictions for regulator-name

On Tue, 2 Aug 2022 08:43:34 +0200, Frieder Schrempf wrote:
> From: Frieder Schrempf <frieder.schrempf@...tron.de>
> 
> The device bindings shouldn't put any constraints on the regulator-name
> property specified in the generic bindings. This allows using arbitrary
> and descriptive names for the regulators.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] dt-bindings: regulator: pca9450: Remove restrictions for regulator-name
      commit: b0de7fa706506bf0591037908376351beda8c5d6

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