[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171171564196.7557.2053181572527484871.b4-ty@kernel.org>
Date: Fri, 29 Mar 2024 12:34:01 +0000
From: Mark Brown <broonie@...nel.org>
To: Seven Lee <wtli@...oton.com>
Cc: lgirdwood@...il.com, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-sound@...r.kernel.org,
krzysztof.kozlowski+dt@...aro.org, linux-kernel@...r.kernel.org,
robh+dt@...nel.org, conor+dt@...nel.org, perex@...ex.cz, tiwai@...e.com,
YHCHuang@...oton.com, KCHSU0@...oton.com, CTLIN0@...oton.com,
SJLIN0@...oton.com, scott6986@...il.com, supercraig0719@...il.com,
dardar923@...il.com
Subject: Re: [PATCH v5 0/2] ASoC: nau8325: Modify driver code and dtschema.
On Wed, 27 Mar 2024 15:57:53 +0800, Seven Lee wrote:
> Revise properties description and use standard units in dtschema.
> The unit conversion driver based on the attribute must also be
> changed accordingly.
>
> Change:
> V1 -> V2:
> - Revise the driver description part for the C++ comment.
> - In the nau8325_clkdet_put function, modify the max variable to hard code.
> - Removed "Clock Detection" switch control.
> - modify the "ALC Enable" switch name.
> - Revise the dtschema for "nuvoton,dac-vref".
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: dt-bindings: Added schema for "nuvoton,nau8325"
commit: 2e4c003b3672085267a358ebf82129b4e08dd64f
[2/2] ASoC: nau8325: new driver
commit: c0a3873b9938bfaa77bd337cad33266a50a6583f
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