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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 06 Jul 2020 15:43:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     catalin.marinas@....com, s.hauer@...gutronix.de,
        shawnguo@...nel.org, Robin Gong <yibin.gong@....com>,
        lgirdwood@...il.com, john.lee@....com, will@...nel.org,
        anson.huang@....com, robh+dt@...nel.org, festevam@...il.com,
        frieder.schrempf@...tron.de
Cc:     linux-imx@....com, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        kernel@...gutronix.de
Subject: Re: [PATCH v2 0/4] Add pca9450 driver

On Sat, 4 Jul 2020 00:19:34 +0800, Robin Gong wrote:
> Add pca9450 driver for i.mx8mn-evk board. PCA9450A/B/C supported now.
> Please refer to below link for PCA9450 datasheet:
> https://www.nxp.com/docs/en/data-sheet/PCA9450DS.pdf
> 
> v2:
>   1. rebase with the latest code to use linear_ranges helper instead.
>   2. address Frieder's comments, such as dulipcated buck4 description,
>      debug info added etc.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: pca9450: add pca9450 pmic driver
      commit: 0935ff5f1f0a44f66a13e075ed49f97ad99d2fdc
[2/2] dt-bindings: regulator: add pca9450 regulator yaml
      commit: 7ae9e3a6bf3fb1b5a35a15d8a6e78fc42bed0867

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

Powered by blists - more mailing lists