linux-kernel - Re: [PATCH] MAINTAINERS: Add Alain Volmat as STM32 SPI maintainer

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: <162135545749.38023.1433793383274689045.b4-ty@kernel.org>
Date:   Tue, 18 May 2021 17:31:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     amelie.delaunay@...s.st.com,
        Alain Volmat <alain.volmat@...s.st.com>
Cc:     Mark Brown <broonie@...nel.org>,
        linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org,
        alexandre.torgue@...s.st.com, linux-kernel@...r.kernel.org,
        mcoquelin.stm32@...il.com, fabrice.gasnier@...s.st.com
Subject: Re: [PATCH] MAINTAINERS: Add Alain Volmat as STM32 SPI maintainer

On Wed, 12 May 2021 07:20:42 +0200, Alain Volmat wrote:
> Add Alain Volmat as STM32 SPI maintainer.

Applied to

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

Thanks!

[1/1] MAINTAINERS: Add Alain Volmat as STM32 SPI maintainer
      commit: d7aed20d446d8c87f5e13adf73281056b0064a45

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