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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 13 Nov 2023 14:05:34 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        liweilei@...nic.com, yijiangtao@...nic.com, trix@...hat.com,
        dan.carpenter@...aro.org, colin.i.king@...il.com,
        herve.codina@...tlin.com, nathan@...nel.org,
        linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
        wangweidong.a@...nic.com
Subject: Re: [PATCH] ASoC: codecs: Modify the bin file parsing method

On Thu, 09 Nov 2023 17:37:07 +0800, wangweidong.a@...nic.com wrote:
> Modify the aw88395_lib file so that the bin file
> parsing is no longer related to the chip id of the chip.
> Adopt the bin file data type "prof_data_type" as the
> differentiation between different chip bin file
> parsing methods.
> 
> Since the chip id macro for the aw88399 is no longer
> defined in aw88395_reg.h, define the chip id
> for the aw88399 in aw88399.h
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: Modify the bin file parsing method
      commit: fc213b8d4466d1fcf39ab760979be4eac2a67635

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ