[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170594122789.63484.12376608294945016367.b4-ty@kernel.org>
Date: Mon, 22 Jan 2024 16:33:47 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-sound@...r.kernel.org,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: p1022_rdk: fix all kernel-doc warnings
On Wed, 10 Jan 2024 20:57:36 -0800, Randy Dunlap wrote:
> Fix several kernel-doc warnings in p1022_rdk.c:
>
> p1022_rdk.c:70: warning: cannot understand function prototype: 'struct machine_data '
> p1022_rdk.c:90: warning: Function parameter or struct member 'card' not described in 'p1022_rdk_machine_probe'
> p1022_rdk.c:90: warning: No description found for return value of 'p1022_rdk_machine_probe'
> p1022_rdk.c:129: warning: Function parameter or struct member 'substream' not described in 'p1022_rdk_startup'
> p1022_rdk.c:129: warning: No description found for return value of 'p1022_rdk_startup'
> p1022_rdk.c:162: warning: Function parameter or struct member 'card' not described in 'p1022_rdk_machine_remove'
> p1022_rdk.c:162: warning: No description found for return value of 'p1022_rdk_machine_remove'
> p1022_rdk.c:187: warning: cannot understand function prototype: 'const struct snd_soc_ops p1022_rdk_ops = '
> p1022_rdk.c:199: warning: Function parameter or struct member 'pdev' not described in 'p1022_rdk_probe'
> p1022_rdk.c:199: warning: No description found for return value of 'p1022_rdk_probe'
> p1022_rdk.c:349: warning: Function parameter or struct member 'pdev' not described in 'p1022_rdk_remove'
> p1022_rdk.c:376: warning: No description found for return value of 'p1022_rdk_init'
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: p1022_rdk: fix all kernel-doc warnings
commit: 90050b8d2e1556238d4c69abc11270de523bf955
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