[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167630512772.2770751.214951401916390841.b4-ty@kernel.org>
Date: Mon, 13 Feb 2023 16:18:47 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
krzysztof.kozlowski@...aro.org, rf@...nsource.cirrus.com,
pierre-louis.bossart@...ux.intel.com,
ckeepax@...nsource.cirrus.com, shumingf@...ltek.com,
herve.codina@...tlin.com, james.schulman@...rus.com,
doug@...morgal.com, yang.lee@...ux.alibaba.com, trix@...hat.com,
colin.i.king@...il.com, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org, wangweidong.a@...nic.com
Cc: liweilei@...nic.com, zhaolei@...nic.com, yijiangtao@...nic.com
Subject: Re: [PATCH 0/3][next] ASoC: codecs: Modify error implicit
declaration of function and misspelling
On Mon, 13 Feb 2023 17:36:46 +0800, wangweidong.a@...nic.com wrote:
> Change the function name aw88395_plack_event to aw88395_playback_event
> Change hdrlen to hdr_len
> Add select GPIOLIB to the sound/soc/codecs/Kconfig file
>
> Weidong Wang (3):
> ASoC: codecs: Fixed a spelling error in the function name
> ASoC: codecs: Modify the log print statement
> ASoC: codecs: Modify error: implicit declaration of function
> 'gpiod_set_value_cansleep'
>
> [...]
Applied to
broonie/sound.git for-next
Thanks!
[1/3] ASoC: codecs: Fixed a spelling error in the function name
commit: 27db41a1f73ad18ed6540e1f8a7083422e5b53d6
[2/3] ASoC: codecs: Modify the log print statement
commit: 14d5d454547adae64a76731c90c37fe33f7d1d44
[3/3] ASoC: codecs: Modify error implicit declaration of function 'gpiod_set_value_cansleep'
commit: 4680716d6a33f50c96eb7ce6ae9cb868baa04438
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