Skip to contentSkip to conversation

MAINTAINERS: add myself as maintainer for spi-fsl-dspi driver

PATCH In review Vladimir Oltean 2 participants 2 messages Aug 21, 2020 – Aug 24, 2020 SPI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: add myself as maintainer for spi-fsl-dspi driver

Since I've introduced a fairly large diff to this driver since tag v5.4, I would like to avoid breakage for my use cases by getting a chance to be copied on newly submitted patches.

---
 MAINTAINERS | 8 ++++++++
 1 file changed, 8 insertions(+)
MAINTAINERS +8 -0
index deaafb617361..d29fa11d7742 100644
@@ -6884,6 +6884,14 @@ L:	[email protected]
 S:	Maintained
 F:	drivers/dma/fsldma.*
 
+FREESCALE DSPI DRIVER
+M:	Vladimir Oltean <[email protected]>
+L:	[email protected]
+S:	Maintained
+F:	Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt
+F:	drivers/spi/spi-fsl-dspi.c
+F:	include/linux/spi/spi-fsl-dspi.h
+
 FREESCALE ENETC ETHERNET DRIVERS
 M:	Claudiu Manoil <[email protected]>
 L:	[email protected]
Signature · 1 line
2.25.1
maintainer
#1 lore raw
Quoted 3 lines · Vladimir Oltean

Since I've introduced a fairly large diff to this driver since tag v5.4, I would like to avoid breakage for my use cases by getting a chance to be copied on newly submitted patches.

Applied to

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

Thanks!

[1/1] MAINTAINERS: add myself as maintainer for spi-fsl-dspi driver

      commit: 3cb5fcf1f3a5dfb7bc0305bb15971db04a0e51d4

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