linux-kernel - Re: [PATCH] regulator: max20411: Fix off-by-one for n

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: <167629805871.2700597.4585542846053690884.b4-ty@kernel.org>
Date:   Mon, 13 Feb 2023 14:20:58 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     Bjorn Andersson <andersson@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: max20411: Fix off-by-one for n_voltages
 setting

On Sat, 11 Feb 2023 23:00:19 +0800, Axel Lin wrote:
> Otherwise regulator_list_voltage returns -EINVAL for MAX20411_MAX_SEL.
> 
> 

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: max20411: Fix off-by-one for n_voltages setting
      commit: 9d1c73191f94c79076b5f46a31b8a1e12b18bc79

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