[PATCH 00/13] ASoC: SOF/Intel: remove __func__ from dev_dbg()
Mark Brown
broonie at kernel.org
Fri Jun 17 18:29:54 CEST 2022
On Thu, 16 Jun 2022 16:53:38 -0500, Pierre-Louis Bossart wrote:
> Cleanups suggested by Greg KH during SoundWire reviews, since the
> __func__ information can be added with the dyndbg kernel parameter
> [1].
>
> The first two patches change the error level in cases where the use of
> dev_dbg() was inconsistent with an aborted programming sequence.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/13] ASoC: SOF: Intel: hda-dsp: report error on power-up/down
commit: 6d5e37b0f343af70a7e824641f264fb140bbead5
[02/13] ASoC: SOF: Intel: hda-stream: report error on stream not opened
commit: 3abc88730a0e45247296a561a12e811b5d2d2236
[03/13] ASoC: SOF: Intel: hda-dai: remove use of __func__ in dev_dbg
commit: 18701bb1370cb6b34a8f3ad820045930138083dc
[04/13] ASoC: SOF: Intel: hda-stream: remove use of __func__ in dev_dbg
commit: 8bf064f8e439d9b92a023a54adc657f920f4e1a8
[05/13] ASoC: SOF: Intel: mtl: remove use of __func__ in dev_dbg
commit: b837870fe17f21cf80b15d143c9ea0bc6b342741
[06/13] ASoC: SOF: ipc3-dtrace: remove use of __func__ in dev_dbg
commit: 9fd8fcd03451ea3f04af9a419748248d3fa8fb59
[07/13] ASoC: SOF: ipc3-loader: remove use of __func__ in dev_dbg
commit: e16809a74f09b2c2e066b3d7cf1d87be2a75911e
[08/13] ASoC: SOF: ipc3-topology: remove use of __func__ in dev_dbg
commit: f132dc020270976fe83c86f8c826890873023980
[09/13] ASoC: SOF: ipc4-topology remove use of __func__ in dev_dbg
commit: 3809264b53906b8b666b93831ecc23a00e119b68
[10/13] ASoC: SOF: sof-client: remove use of __func__ in dev_dbg
commit: 298e3aba1b56d19dcb70e10ffe93057d1ddd18f6
[11/13] ASoC: SOF: ipc4: remove use of __func__ in dev_dbg
commit: b3ec3eb2baaad057631ab7e09c38ab3ad5c7a42b
[12/13] ASoC: Intel: boards: hda: remove use of __func__ in dev_dbg
commit: 46bc6bc3a6a3af5306e8e3320a083cf3c32350d4
[13/13] ASoC: Intel: boards: sof_sdw: remove use of __func__ in dev_dbg
commit: d2d19cb6ed13eb54dd6c958f3808a23820c3ebba
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
More information about the Alsa-devel
mailing list