linux-kernel - Re: [PATCH v5 0/2] regulator: aw37503: add regulator driver for Awinic AW37503

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: <169272202114.71818.13706933583974169859.b4-ty@kernel.org>
Date:   Tue, 22 Aug 2023 17:33:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
        like@...nic.com
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        liweilei@...nic.com, liangdong@...nic.com, wangweidong.a@...nic.com
Subject: Re: [PATCH v5 0/2] regulator: aw37503: add regulator driver for
 Awinic AW37503

On Mon, 21 Aug 2023 03:53:53 +0000, like@...nic.com wrote:
> Add regulator driver for the device Awinic AW37503 which is
> single inductor - dual output power supply device. AW37503
> device is designed to support general positive/negative
> driven applications like TFT display panels.
> 
> v4->v5: Delete the unnecessary '|' in the awinic,aw37503.yaml.
> v3->v4: Correct yamllint warnings/errors.
> v2->v3: Switch to use the dev_err_probe().
>         Keep the Kconfig and Makefile sorted.
>         Correct yamllint warnings/errors.
> v1->v2: Remove unneeded fields and correct yamllint warnings/errors.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: aw37503: add regulator driver for Awinic AW37503
      commit: 2796a01cdf2c639e605088c53a1ac36923ade93c
[2/2] regulator: dt-bindings: Add Awinic AW37503
      commit: 86a1b61a0c7316febecd03d47eaf893eb5a57659

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