linux-kernel - Re: [PATCH 0/2] regulator: Introduce UniPhier NX1 SoC support

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: <163486395941.2610269.5320640167922930528.b4-ty@kernel.org>
Date:   Fri, 22 Oct 2021 01:52:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
        Rob Herring <robh+dt@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] regulator: Introduce UniPhier NX1 SoC support

On Mon, 18 Oct 2021 10:30:03 +0900, Kunihiko Hayashi wrote:
> This series includes the patches to add basic support for new UniPhier NX1
> SoC. NX1 SoC also has the same kinds of controls as the other UniPhier
> SoCs.
> 
> Kunihiko Hayashi (2):
>   dt-bindings: regulator: uniphier: Add binding for NX1 SoC
>   regulator: uniphier: Add USB-VBUS compatible string for NX1 SoC
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: uniphier: Add binding for NX1 SoC
      commit: 4c1ef56bd9c7a60efdeac9f1478b5467fb47c093
[2/2] regulator: uniphier: Add USB-VBUS compatible string for NX1 SoC
      commit: 32e84faa825e8bc6431186a41b68e0fcff857b72

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