[PATCH 0/2] MAINTAINERS: update Socionext SPI maintainer addresses

Johan Hovold posted 2 patches 2 months ago
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
[PATCH 0/2] MAINTAINERS: update Socionext SPI maintainer addresses
Posted by Johan Hovold 2 months ago
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(-)

-- 
2.52.0
Re: [PATCH 0/2] MAINTAINERS: update Socionext SPI maintainer addresses
Posted by Mark Brown 2 months ago
On Fri, 10 Apr 2026 10:34:21 +0200, Johan Hovold wrote:
> 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