Skip to contentSkip to conversation

MAINTAINERS: Update Cirrus Logic parts to linux-sound mailing list

PATCH In review Charles Keepax 2 participants 2 messages Aug 7, 2024 – Aug 8, 2024 Sound

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: Update Cirrus Logic parts to linux-sound mailing list

Now that most kernel work on sound has moved over to the linux-sound mailing list so should the Cirrus Logic audio parts.

---
 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
MAINTAINERS +2 -2
index 88a40557db32..5babee26f20c 100644
@@ -5306,7 +5306,7 @@ F:	drivers/media/cec/i2c/ch7322.c
 CIRRUS LOGIC AUDIO CODEC DRIVERS
 M:	David Rhodes <[email protected]>
 M:	Richard Fitzgerald <[email protected]>
-L:	[email protected] (moderated for non-subscribers)
+L:	[email protected]
 L:	[email protected]
 S:	Maintained
 F:	Documentation/devicetree/bindings/sound/cirrus,cs*
@@ -5375,7 +5375,7 @@ F:	sound/soc/codecs/lochnagar-sc.c
 CIRRUS LOGIC MADERA CODEC DRIVERS
 M:	Charles Keepax <[email protected]>
 M:	Richard Fitzgerald <[email protected]>
-L:	[email protected] (moderated for non-subscribers)
+L:	[email protected]
 L:	[email protected]
 S:	Supported
 W:	https://github.com/CirrusLogic/linux-drivers/wiki
Signature · 1 line
2.39.2
#1 lore raw
Quoted 4 lines · Charles Keepax

Now that most kernel work on sound has moved over to the linux-sound mailing list so should the Cirrus Logic audio parts.

Applied to

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

Thanks!

[1/1] MAINTAINERS: Update Cirrus Logic parts to linux-sound mailing list

      commit: 2f11f61f9d4d5692bcebb9d089429ee0c046e08a

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