linux-kernel - Re: [PATCH V4 0/2] ASoC: codecs: Add aw88083 amplifier 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]

Message-Id: <173627914448.519339.12595534699937651368.b4-ty@kernel.org>
Date: Tue, 07 Jan 2025 19:45:44 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, robh@...nel.org, krzk+dt@...nel.org, 
 conor+dt@...nel.org, perex@...ex.cz, tiwai@...e.com, jack.yu@...ltek.com, 
 rf@...nsource.cirrus.com, neil.armstrong@...aro.org, 
 ivprusov@...utedevices.com, luca.ceresoli@...tlin.com, 
 zhoubinbin@...ngson.cn, quic_pkumpatl@...cinc.com, herve.codina@...tlin.com, 
 masahiroy@...nel.org, nuno.sa@...log.com, yesanishhere@...il.com, 
 linux-sound@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org, wangweidong.a@...nic.com
Cc: yijiangtao@...nic.com
Subject: Re: [PATCH V4 0/2] ASoC: codecs: Add aw88083 amplifier driver

On Tue, 31 Dec 2024 20:56:08 +0800, wangweidong.a@...nic.com wrote:
> Add the awinic,aw88083 property to support the aw88083 chip.
> 
> The driver is for amplifiers aw88083 of Awinic Technology
> Corporation. The AW88083 is an intelligent digital audio
> amplifier with low noise.
> 
> v3 -> v4: Modify the commit message
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: Add schema for "awinic,aw88083"
      commit: e7b73981380cefc9ed6261e3b53c37c327cab189
[2/2] ASoC: codecs: Add aw88083 amplifier driver
      commit: c51187903fe4523fd7f521662c1ae1f1f3174036

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