linux-kernel - Re: [PATCH v3 0/6] regulator: mcp16502: add support for ramp delay

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: <160683107676.35139.5462793420865249234.b4-ty@kernel.org>
Date:   Tue, 01 Dec 2020 13:57:56 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, Claudiu Beznea <claudiu.beznea@...rochip.com>
Cc:     s.hauer@...gutronix.de, axel.lin@...ics.com,
        linux-arm-kernel@...ts.infradead.org, ttynkkynen@...dia.com,
        linux-kernel@...r.kernel.org, linus.walleij@...aro.org
Subject: Re: [PATCH v3 0/6] regulator: mcp16502: add support for ramp delay

On Fri, 13 Nov 2020 17:21:04 +0200, Claudiu Beznea wrote:
> This series adds support for ramp delay on mcp16502. It also adds
> some cleanup on mcp16502.
> 
> Apart from that patches 1/6 fixes the selector validation in case
> the regulator::desc::linear_min_sel is not zero.
> 
> Thank you,
> Claudiu Beznea
> 
> [...]

Applied to

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

Thanks!

[1/6] regulator: core: validate selector against linear_min_sel
      (no commit info)
[2/6] regulator: core: do not continue if selector match
      (no commit info)
[3/6] regulator: mcp16502: add linear_min_sel
      (no commit info)
[4/6] regulator: mcp16502: adapt for get/set on other registers
      (no commit info)
[5/6] regulator: mcp16502: add support for ramp delay
      (no commit info)
[6/6] regulator: mcp16502: remove void documentation of struct mcp16502
      (no commit info)

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