linux-kernel - Re: [PATCH] regulator: sm5703: Correct reference to the common regulator schema

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]

Date:   Fri, 29 Apr 2022 14:39:31 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, markuss.broks@...il.com,
        robh+dt@...nel.org, lee.jones@...aro.org
Cc:     krzysztof.kozlowski+dt@...aro.org, lgirdwood@...il.com,
        devicetree@...r.kernel.org
Subject: Re: [PATCH] regulator: sm5703: Correct reference to the common regulator schema

On Fri, 29 Apr 2022 15:09:14 +0300, Markuss Broks wrote:
> The correct file name is regulator.yaml, not regulators.yaml.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: sm5703: Correct reference to the common regulator schema
      commit: dc6d04619e62825083926929d88c94c5b6b42670

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