linux-kernel - Re: [PATCH V2 0/3] ASoC: codecs: Modify some error codes

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: <169893518558.36738.243491245634528224.b4-ty@kernel.org>
Date:   Thu, 02 Nov 2023 14:26:25 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        liweilei@...nic.com, u.kleine-koenig@...gutronix.de,
        yang.lee@...ux.alibaba.com, nathan@...nel.org,
        linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
        wangweidong.a@...nic.com
Subject: Re: [PATCH V2 0/3] ASoC: codecs: Modify some error codes

On Wed, 01 Nov 2023 17:02:07 +0800, wangweidong.a@...nic.com wrote:
> The maximum value that calib can set should be
> consistent with the maximum value of re.
> 
> An error code should be return when the re is greater
> than the maximum value or less than the minimum value
> 
> The value of vsense_select should be either 32
> or 0 in both cases, so modify the
> AW88399_DEV_VDSEL_VSENSE macro to 32.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: codecs: Modify the maximum value of calib
      commit: c9e920ffa752b9047d65041cd70495409c768dd7
[2/3] ASoC: codecs: Modify the wrong judgment of re value
      commit: baf46c3c763809fbeabcff5ec6e2ff3081f755f2
[3/3] ASoC: codecs: Modify macro value error
      commit: b729598c1747576bb9a4c997190be3f7c2915726

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