Skip to contentSkip to conversation

MAINTAINERS: remove Timur Tabi from Freescale SOC sound drivers

PATCH In review Timur Tabi 3 participants 3 messages Jun 20, 2021 – Jun 21, 2021

lore
Share & tools
lore

Timur Tabi

author
#0 lore raw

PATCH 1/1 MAINTAINERS: remove Timur Tabi from Freescale SOC sound drivers

I haven't touched these drivers in seven years, and none of the patches sent to me these days affect code that I wrote. The other maintainers are doing a very good job without me.

---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)
MAINTAINERS +0 -1
index 8c5ee008301a..b3b9a253316f 100644
@@ -7354,7 +7354,6 @@ F:	drivers/net/ethernet/freescale/fs_enet/
 F:	include/linux/fs_enet_pd.h
 
 FREESCALE SOC SOUND DRIVERS
-M:	Timur Tabi <[email protected]>
 M:	Nicolin Chen <[email protected]>
 M:	Xiubo Li <[email protected]>
 R:	Fabio Estevam <[email protected]>
Signature · 1 line
2.25.1
#2 lore raw
In reply to Timur Tabi
Quoted 3 lines · Timur Tabi

I haven't touched these drivers in seven years, and none of the patches sent to me these days affect code that I wrote. The other maintainers are doing a very good job without me.

Applied to

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

Thanks!

[1/1] MAINTAINERS: remove Timur Tabi from Freescale SOC sound drivers

      commit: 50b1ce617d66d04f1f9006e51793e6cffcdec6ea

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