Skip to contentSkip to conversation

ASoC: cs35l56: Sort table of sdw_device_id

PATCH In review Richard Fitzgerald 2 participants 2 messages Jul 22 – Jul 24

Subsystems (3)
lore
Share & tools
lore

Richard Fitzgerald

author maintainer
#0 lore raw

PATCH 1/1 ASoC: cs35l56: Sort table of sdw_device_id

Swap the entries for 3562 and 3563 to keep the table in order of increasing part number.

There's nothing broken here, it's just cosmetic.

---
 sound/soc/codecs/cs35l56-sdw.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/cs35l56-sdw.c +1 -1
index 1e442f43b306..303d37e7d0bf 100644
@@ -510,8 +510,8 @@ static const struct dev_pm_ops cs35l56_sdw_pm = {
 static const struct sdw_device_id cs35l56_sdw_id[] = {
 	SDW_SLAVE_ENTRY(0x01FA, 0x3556, 0x3556),
 	SDW_SLAVE_ENTRY(0x01FA, 0x3557, 0x3557),
-	SDW_SLAVE_ENTRY(0x01FA, 0x3563, 0x3563),
 	SDW_SLAVE_ENTRY(0x01FA, 0x3562, 0x3562),
+	SDW_SLAVE_ENTRY(0x01FA, 0x3563, 0x3563),
 	{},
 };
 MODULE_DEVICE_TABLE(sdw, cs35l56_sdw_id);
Signature · 1 line
2.47.3
maintainer
#1 lore raw
Quoted 1 line · Richard Fitzgerald

ASoC: cs35l56: Sort table of sdw_device_id

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3

Thanks!

[1/1] ASoC: cs35l56: Sort table of sdw_device_id

      https://git.kernel.org/broonie/sound/c/998b8a6c8aff

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