linux-kernel - Re: [PATCH] MAINTAINERS: Add myself as a maintainer for Microchip SPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <168915816580.10699.2252199875288526043.b4-ty@kernel.org>
Date:   Wed, 12 Jul 2023 11:36:05 +0100
From:   Mark Brown <broonie@...nel.org>
To:     tudor.ambarus@...aro.org, linux-kernel@...r.kernel.org,
        Ryan.Wanner@...rochip.com
Subject: Re: [PATCH] MAINTAINERS: Add myself as a maintainer for Microchip
 SPI

On Fri, 30 Jun 2023 09:17:00 -0700, Ryan.Wanner@...rochip.com wrote:
> Tudor is not with Microchip anymore. I have worked lately
> with Microchip SPI drivers replacing Tudor with myself as this
> maintainer.
> 
> 

Applied to

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

Thanks!

[1/1] MAINTAINERS: Add myself as a maintainer for Microchip SPI
      commit: c09168c9392ac9250d87d71fc5ca3156f7456ea4

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