linux-kernel - Re: [PATCH v5 0/6] Fix issues on pf8x00 driver

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, 15 Jan 2021 18:19:51 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Adrien Grassein <adrien.grassein@...il.com>
Cc:     robh+dt@...nel.org, linux-kernel@...r.kernel.org,
        jagan@...rulasolutions.com, devicetree@...r.kernel.org,
        lgirdwood@...il.com
Subject: Re: [PATCH v5 0/6] Fix issues on pf8x00 driver

On Thu, 14 Jan 2021 18:47:08 +0100, Adrien Grassein wrote:
> this patch set aims is to fix some issues contains in the pf8x00 driver.
> Some issues are documentation ones, some others are in code.
> 
> These issues where found while developing another version of the same
> driver. I prefer to share with you the patch for it.
> 
> I do these patches on the master branch of the linux-next repository.
> 
> [...]

Applied to

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

Thanks!

[1/6] regulator: pf8x00: add a doc for the module
      commit: 4d23b84d1fcd1eadbc5c6cd93e76b02a8d191d66
[2/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc
      commit: 988d0d42509a2c1fad0844a6e8f9c7bce7c930dd
[3/6] regulator: dt-bindings: pf8x00: mark nxp,ilim-ma property as deprecated
      commit: 34b860aa0b6221b21eea6bac76357063f525b561
[4/6] regulator: pf8x00: mark nxp,ilim-ma property as deprecated
      commit: 245f5f65229a6c6f5b04fa90221b44818a928916
[5/6] regulator: pf8x00: use linear range for buck 1-6
      commit: 35a93349932e0e04c284f8a4954f3d1236c97d85
[6/6] regulator: pf8x00: fix nxp,phase-shift
      commit: 475a5d85ff62f7ca73f51f23977e7e3ec8c9f906

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