On 15 Mar 2021 09:57:14 +0900, Kuninori Morimoto wrote:
> Indicating error message when failed case is very useful for debuging.
> In many case, it uses below style.
>
> int function(...)
> {
> ...
> return ret;
> }
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/14] ASoC: soc-pcm: indicate error message at soc_pcm_open()
commit: e4b044f4582366de10b8b28614c24ac4ff22b299
[02/14] ASoC: soc-pcm: indicate error message at soc_pcm_hw_params()
commit: cb11f79b4af65005584880eb408f9748c32661d0
[03/14] ASoC: soc-pcm: indicate error message at soc_pcm_prepare()
commit: dab7eeb4045cce074e083be1f3092d7390d6cfb2
[04/14] ASoC: soc-pcm: indicate error message at dpcm_path_get()
commit: d479f00b795ac62b24ef90f4ec421e65c3178ca7
[05/14] ASoC: soc-pcm: indicate error message at dpcm_be_dai_trigger()
commit: db3aa39c91068424407f71d23b028493eac994a1
[06/14] ASoC: soc-pcm: indicate error message at dpcm_apply_symmetry()
commit: bbd2bac8d6ca00ee0b032d3c03100328131425ac
[07/14] ASoC: soc-pcm: indicate error message at dpcm_run_update_startup/shutdown()
commit: 81c82a9edbddc4cd97e4d974dfd7f2689ee63474
[08/14] ASoC: soc-pcm: indicate error message at dpcm_fe/be_dai_startup()
commit: 06aaeb874256a10fe5b84f511da3c65f548a43b9
[09/14] ASoC: soc-pcm: indicate error message at dpcm_fe/be_dai_hw_params()
commit: 33b6b94f55ec60517ce71ca2bc9c03a6d337c805
[10/14] ASoC: soc-pcm: indicate error message at dpcm_fe/be_dai_prepare()
commit: 273db971cf833d62c9e2d9381d190e14b1cd3641
[11/14] ASoC: soc-pcm: don't indicate error message for soc_pcm_hw_free()
commit: e20c9c4f96d79aa48eb3649c57f1f2784f92b838
[12/14] ASoC: soc-pcm: don't indicate error message for dpcm_be_dai_hw_free()
commit: f52366e6831ecb2da133b6ecfc7c69266086660c
[13/14] ASoC: don't indicate error message for snd_soc_[pcm_]dai_xxx()
commit: 62462e018220895267450155b188f5804f54c202
[14/14] ASoC: don't indicate error message for snd_soc_[pcm_]component_xxx()
commit: 60adbd8fbf486214f4ae1946e61df69c3867e20b
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
