[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168623753047.1002486.1442664487202243971.b4-ty@kernel.org>
Date: Thu, 08 Jun 2023 16:18:50 +0100
From: Mark Brown <broonie@...nel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
matthias.bgg@...il.com, trevor.wu@...iatek.com,
amergnat@...libre.com, dan.carpenter@...aro.org,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, kernel@...labora.com
Subject: Re: [PATCH 0/5] ASoC: mt8188-mt6359: Cleanups
On Thu, 08 Jun 2023 10:47:22 +0200, AngeloGioacchino Del Regno wrote:
> This series performs some cleanups to the mt8188-mt6359 driver,
> including usage of bitfield macros, adding definitions of register
> fields and some others for readability and consistency.
>
> AngeloGioacchino Del Regno (4):
> ASoC: mediatek: mt8188-mt6359: Compress of_device_id entries
> ASoC: mediatek: mt8188-mt6359: Cleanup return 0 disguised as return
> ret
> ASoC: mediatek: mt8188-mt6359: Clean up log levels
> ASoC: mediatek: mt8188-mt6359: Use bitfield macros for registers
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: mediatek: mt8188-mt6359: Compress of_device_id entries
commit: 22628e92d76a403181916f7bac7848dd2326d750
[2/5] ASoC: mediatek: mt8188-mt6359: clean up a return in codec_init
commit: 1148b42257e2bf30093708398db2c4570ae9fe97
[3/5] ASoC: mediatek: mt8188-mt6359: Cleanup return 0 disguised as return ret
commit: 4882ef44f51bbb759b8a738b747fdbcbad38e51b
[4/5] ASoC: mediatek: mt8188-mt6359: Clean up log levels
commit: acb43baf8b7e75acdb14920de29881e3f70c6819
[5/5] ASoC: mediatek: mt8188-mt6359: Use bitfield macros for registers
commit: b0e2e4fb8a5467f4f64bcf64d1454d18cb665cc8
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