Message ID | 20240821070815.2326534-1-lihongbo22@huawei.com (mailing list archive) |
---|---|
Headers | show |
Series | sound/soc: fix some macro definitions and usages | expand |
On Wed, Aug 21, 2024 at 03:08:10PM +0800, Hongbo Li wrote: > Hongbo Li (5): > sound/soc: fix macro definition on TWL4030_OUTPUT_PGA > sound/soc remove unused substream in macro soc_component_mark_pop > sound/soc remove unused substream in macro soc_dai_mark_pop > sound/soc remove unused substream in macro soc_link_mark_pop > sound/soc: fix macro definition on STM_SAI_HAS_EXT_SYNC Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.
On Wed, 21 Aug 2024 15:08:10 +0800, Hongbo Li wrote: > Many variable in macro are not used as we used macro_check > script to detect and mamually check, let us address these > issues. > > Hongbo Li (5): > sound/soc: fix macro definition on TWL4030_OUTPUT_PGA > sound/soc remove unused substream in macro soc_component_mark_pop > sound/soc remove unused substream in macro soc_dai_mark_pop > sound/soc remove unused substream in macro soc_link_mark_pop > sound/soc: fix macro definition on STM_SAI_HAS_EXT_SYNC > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/5] sound/soc: fix macro definition on TWL4030_OUTPUT_PGA commit: ac9fc25f114aec07e7f5348606c9702f8377f44a [2/5] sound/soc remove unused substream in macro soc_component_mark_pop commit: 5687851e484bdb22fa565578e0b046a50d502941 [3/5] sound/soc remove unused substream in macro soc_dai_mark_pop commit: 7215afbd8c090a3254f8cadabb550adf1c00547f [4/5] sound/soc remove unused substream in macro soc_link_mark_pop commit: 2f12d0de77b99f0f35755d16efeb12e6f45e5710 [5/5] sound/soc: fix macro definition on STM_SAI_HAS_EXT_SYNC commit: 7a01e17e42fe944982acde1dd40bdea177372173 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