[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172780520098.2298697.10488363021323219650.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 18:53:20 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Igor Prusov <ivprusov@...utedevices.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org, kernel@...utedevices.com, prusovigor@...il.com,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v3 0/6] ASoC: Add NTP8918 and NTP8835 codecs support
On Wed, 25 Sep 2024 17:52:38 +0300, Igor Prusov wrote:
> This series adds support for two NeoFidelity amplifiers. For both
> amplifiers vendor provides software for equalizer and filters
> configuration, which generates firmware files with registers values.
> Since in both cases those files have same encoding, a common helper
> module is added to get firmware via request_firmware() API and set
> registers values.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] dt-bindings: vendor-prefixes: Add NeoFidelity, Inc
commit: 5d9e6d6fc1b98c8c22d110ee931b3b233d43cd13
[2/6] ASoC: codecs: Add NeoFidelity Firmware helpers
commit: ba1850dc0f2b5638a4a6aa16905c1856dc17587b
[3/6] ASoC: dt-bindings: Add NeoFidelity NTP8918
commit: 64fbb6bdd45b8953fcad5c4ec648f74c96aec5f3
[4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec
commit: 2bd61fff3e93b93a20f618028433bcbe8329a6db
[5/6] ASoC: dt-bindings: Add NeoFidelity NTP8835
commit: 3e2aba5f0b0cafad44c2f635dc19d7bf3f54b978
[6/6] ASoC: codecs: Add NeoFidelity NTP8835 codec
commit: dc9004ea273a9141c16b90a687da70b77f5a640a
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