[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <169815572396.69390.16547597734984966966.b4-ty@kernel.org>
Date: Tue, 24 Oct 2023 14:55:23 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
perex@...ex.cz, tiwai@...e.com, shumingf@...ltek.com,
rf@...nsource.cirrus.com, herve.codina@...tlin.com,
ckeepax@...nsource.cirrus.com, 13916275206@....com,
ryans.lee@...log.com, linus.walleij@...aro.org,
sebastian.reichel@...labora.com,
ajye_huang@...pal.corp-partner.google.com,
harshit.m.mogalapalli@...cle.com, arnd@...db.de,
colin.i.king@...il.com, dan.carpenter@...aro.org, trix@...hat.com,
liweilei@...nic.com, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
wangweidong.a@...nic.com
Cc: yijiangtao@...nic.com
Subject: Re: [PATCH V2 0/4] ASoC: codecs: Add aw88399 amplifier driver
On Fri, 20 Oct 2023 16:34:22 +0800, wangweidong.a@...nic.com wrote:
> Add the awinic,aw88399 property to the awinic,aw88395.yaml file.
>
> Add i2c and amplifier registration for
> aw88399 and their associated operation functions.
>
> v1 -> v2: Modify the reset mode
> Delete AW88399_DSP_I2C_WRITES macros
> and related debugging statements
> Change the value of max_register in aw88399
> Change the value of max_register in aw88261
> Delete the judgment of unnecessary pointers
> Modify the judgment of the ret return value
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: dt-bindings: Add schema for "awinic,aw88399"
(no commit info)
[2/4] ASoC: codecs: Modify max_register usage error
commit: f1c406866af5dacdd9601cfa3be4873ebd801b86
[3/4] ASoC: codecs: Add code for bin parsing compatible with aw88399
(no commit info)
[4/4] ASoC: codecs: Add aw88399 amplifier driver
(no commit info)
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