I noticed the driver is unclaimed. Since I was the last one doing
substantial work on it, add me as the maintainer.
As it is only found in legacy products, mark it as "Odd Fixes"
instead of "Maintained".
Signed-off-by: Jonas Gorski <[email protected]>
---
v1 -> v2:
* fix the driver's file name
* include the right people
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index bc201627c2e0..2594a0643e0a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4169,6 +4169,13 @@ F: Documentation/devicetree/bindings/spi/brcm,bcm63xx-hsspi.yaml
F: drivers/spi/spi-bcm63xx-hsspi.c
F: drivers/spi/spi-bcmbca-hsspi.c
+BROADCOM BCM6348/BCM6358 SPI controller DRIVER
+M: Jonas Gorski <[email protected]>
+L: [email protected]
+S: Odd Fixes
+F: Documentation/devicetree/bindings/spi/spi-bcm63xx.txt
+F: drivers/spi/spi-bcm63xx.c
+
BROADCOM ETHERNET PHY DRIVERS
M: Florian Fainelli <[email protected]>
R: Broadcom internal kernel review list <[email protected]>
--
2.34.1
On 7/8/2023 9:53 PM, Jonas Gorski wrote:
> I noticed the driver is unclaimed. Since I was the last one doing
> substantial work on it, add me as the maintainer.
>
> As it is only found in legacy products, mark it as "Odd Fixes"
> instead of "Maintained".
>
> Signed-off-by: Jonas Gorski <[email protected]>
Acked-by: Florian Fainelli <[email protected]>
--
Florian
On Sat, 08 Jul 2023 21:53:08 +0200, Jonas Gorski wrote:
> I noticed the driver is unclaimed. Since I was the last one doing
> substantial work on it, add me as the maintainer.
>
> As it is only found in legacy products, mark it as "Odd Fixes"
> instead of "Maintained".
>
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] MAINTAINERS: add myself for spi-bcm63xx
commit: 2bbc72ffc4de803f6265119963aa7aac6559960f
[2/2] mailmap: add entry for Jonas Gorski
commit: 54ccc8758ef4d29de9e8fdb711c852abbdd4103a
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