linux-kernel - Re: [PATCH v2 0/2] Add Richtek RT5759 buck converter 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: <164933597780.2466529.16895833631668270427.b4-ty@kernel.org>
Date:   Thu, 07 Apr 2022 13:52:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, u0084500@...il.com
Cc:     linux-kernel@...r.kernel.org, cy_huang@...htek.com,
        devicetree@...r.kernel.org, gene_chen@...htek.com,
        lgirdwood@...il.com
Subject: Re: [PATCH v2 0/2] Add Richtek RT5759 buck converter support

On Sat, 26 Mar 2022 19:39:46 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@...htek.com>
> 
> This patch series add Richtek RT5759 buck converter support.
> 
> since V2
> - Fix typo in title description.
> - Put allOf and if/then to be together.
> - Change node name to generic 'regulator'.
> - Remove seperate wdt_enable variable.
> - Add of_match_ptr in struct driver of_match_table declaration.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: Add binding for Richtek RT5759 DCDC converter
      commit: 2a826d9c4251e4a64aa79113aac8cedf7cd0ff57
[2/2] regulator: rt5759: Add support for Richtek RT5759 DCDC converter
      commit: 7b36ddb208bd1744f4769f11e530bc08c3701964

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