[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169143806017.302632.37564599708375249.b4-ty@kernel.org>
Date: Mon, 07 Aug 2023 20:54:20 +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, rf@...nsource.cirrus.com,
shumingf@...ltek.com, herve.codina@...tlin.com,
13916275206@....com, ryans.lee@...log.com,
ckeepax@...nsource.cirrus.com, sebastian.reichel@...labora.com,
ajye_huang@...pal.corp-partner.google.com, povik+lin@...ebit.org,
yijiangtao@...nic.com, trix@...hat.com, colin.i.king@...il.com,
liweilei@...nic.com, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
wangweidong.a@...nic.com
Cc: zhangjianming@...nic.com
Subject: Re: [PATCH V4 0/3] ASoC: codecs: Add awinic AW88261 audio
amplifier driver
On Fri, 04 Aug 2023 19:47:46 +0800, wangweidong.a@...nic.com wrote:
> The awinic AW88261 is an I2S/TDM input, high efficiency
> digital Smart K audio amplifier
>
> v3 -> v4: Modify the dev_err_probe usage
> Changed the use of sizeof in kzalloc
> Changed the function name
> Merge aw88261_device.c into aw88261.c
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: dt-bindings: Add schema for "awinic,aw88261"
commit: 517d52ae5cf75d55970345ece4f6743abdf4620f
[2/3] ASoC: codecs: Add code for bin parsing compatible with aw88261
commit: 7f4ec77802aa17518990ed954bf536fd3bcf25cb
[3/3] ASoC: codecs: Add aw88261 amplifier driver
commit: 028a2ae256916eeae1040049d2d0129535ace60e
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