linux-kernel - Re: [PATCH v6 1/5] dt-bindings: vendor-prefixes: Add Shanghai FourSemi Semiconductor Co.,Ltd

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: <175501583828.192378.16681495842244137315.b4-ty@kernel.org>
Date: Tue, 12 Aug 2025 17:23:58 +0100
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, 
 Nick Li <nick.li@...rsemi.com>
Cc: xiaoming.yang@...rsemi.com, danyang.zheng@...rsemi.com, 
 like.xy@...mail.com, linux-sound@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v6 1/5] dt-bindings: vendor-prefixes: Add Shanghai
 FourSemi Semiconductor Co.,Ltd

On Mon, 11 Aug 2025 18:46:06 +0800, Nick Li wrote:
> Add vendor prefix for Shanghai FourSemi Semiconductor Co.,Ltd
> Link: https://en.foursemi.com/
> 
> 

Applied to

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

Thanks!

[1/5] dt-bindings: vendor-prefixes: Add Shanghai FourSemi Semiconductor Co.,Ltd
      commit: 243167e96939630b7d0d7f61be926d327e14a017
[2/5] ASoC: dt-bindings: Add FS2104/5S audio amplifiers
      commit: fd90680da7e2d92e50ad72dfd4ea601098ab3493
[3/5] ASoC: codecs: Add library for FourSemi audio amplifiers
      commit: e0bbbcaceba1cf47751f264d0dbe36206eab0ef0
[4/5] ASoC: codecs: Add FourSemi FS2104/5S audio amplifier driver
      commit: 75611770177965ae902c87c96eace07542beff07
[5/5] MAINTAINERS: Add entry for FourSemi audio amplifiers
      commit: 2291a2186305faaf8525d57849d8ba12ad63f5e7

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