Skip to contentSkip to conversation

MAINTAINERS: update Socionext SPI maintainer addresses

PATCH In review Johan Hovold 3 participants 5 messages Apr 10 – Apr 14 SPI

lore
Share & tools
lore
#0 lore raw

cover MAINTAINERS: update Socionext SPI maintainer addresses

The Linaro addresses of the Socionext SPI maintainers are bouncing. Update the entries using addresses also found in MAINTAINERS.

Johan

Johan Hovold (2):
MAINTAINERS: update Socionext SPI maintainer address
MAINTAINERS: update second Socionext SPI maintainer address

 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.52.0
#1 lore raw

PATCH 1/2 MAINTAINERS: update Socionext SPI maintainer address

The Linaro address is bouncing so switch to Masahisa's Socionext address also found in MAINTAINERS.

Cc Masahisa Kojima <[email protected]>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
MAINTAINERS +1 -1
index 213f6a294a9f..e22dcbeb7132 100644
@@ -24465,7 +24465,7 @@ F:	Documentation/devicetree/bindings/net/socionext,synquacer-netsec.yaml
 F:	drivers/net/ethernet/socionext/netsec.c
 
 SOCIONEXT (SNI) Synquacer SPI DRIVER
-M:	Masahisa Kojima <[email protected]>
+M:	Masahisa Kojima <[email protected]>
 M:	Jassi Brar <[email protected]>
 L:	[email protected]
 S:	Maintained
Signature · 1 line
2.52.0
#3 lore raw

PATCH 2/2 MAINTAINERS: update second Socionext SPI maintainer address

In reply to Johan Hovold

The Linaro address is bouncing so switch to Jassi's gmail address also found in MAINTAINERS.

---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
MAINTAINERS +1 -1
index e22dcbeb7132..8e829c4b7801 100644
@@ -24466,7 +24466,7 @@ F:	drivers/net/ethernet/socionext/netsec.c
 
 SOCIONEXT (SNI) Synquacer SPI DRIVER
 M:	Masahisa Kojima <[email protected]>
-M:	Jassi Brar <[email protected]>
+M:	Jassi Brar <[email protected]>
 L:	[email protected]
 S:	Maintained
 F:	Documentation/devicetree/bindings/spi/socionext,synquacer-spi.yaml
Signature · 1 line
2.52.0
Acked-by on v1 1/2
#2 lore raw

RE: [PATCH 1/2] MAINTAINERS: update Socionext SPI maintainer address

In reply to Johan Hovold

Hi Johan,

Quoted 29 lines

-----Original Message-----
From: Johan Hovold <[email protected]>
Sent: Friday, April 10, 2026 5:34 PM
To: Mark Brown <[email protected]>
Cc: [email protected]; Jassi
Brar <[email protected]>; [email protected]; [email protected]; Johan Hovold <[email protected]>
Subject: [PATCH 1/2] MAINTAINERS: update Socionext SPI maintainer address

The Linaro address is bouncing so switch to Masahisa's Socionext address also found in MAINTAINERS.

Cc Masahisa Kojima <[email protected]>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
MAINTAINERS +0 -0
index 213f6a294a9f..e22dcbeb7132 100644
@@ -24465,7 +24465,7 @@ F:
 	Documentation/devicetree/bindings/net/socionext,synquacer-netse

c.yaml
F: drivers/net/ethernet/socionext/netsec.c

SOCIONEXT (SNI) Synquacer SPI DRIVER

MAINTAINERS F: Documentation/devicetree/bindings/net/socionext,synquacer-netsec.yaml · line 24468

Quoted 2 lines
MAINTAINERS +1 -1
-M:	Masahisa Kojima <[email protected]>
+M:	Masahisa Kojima <[email protected]>

Thank you for the fix.

Best regards,
Masahisa Kojima

Quoted 5 lines

M: Jassi Brar <[email protected]>
L: [email protected]
S: Maintained
--
2.52.0

maintainer
#4 lore raw
In reply to Johan Hovold
Quoted 8 lines · Johan Hovold

MAINTAINERS: update Socionext SPI maintainer addresses

The Linaro addresses of the Socionext SPI maintainers are bouncing. Update the entries using addresses also found in MAINTAINERS.

Johan

[...]

Applied to

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

Thanks!

[1/2] MAINTAINERS: update Socionext SPI maintainer address

      https://git.kernel.org/broonie/spi/c/9c53a0379e29
[2/2] MAINTAINERS: update second Socionext SPI maintainer address
      https://git.kernel.org/broonie/spi/c/978df761538e

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