linux-kernel - Re: [PATCH] MAINTAINERS: adjust file entry in RISC-V MICROCHIP SUPPORT

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: <176350770659.1411024.1566191077939342244.b4-ty@kernel.org>
Date: Tue, 18 Nov 2025 23:15:06 +0000
From: Mark Brown <broonie@...nel.org>
To: Prajna Rajendra Kumar <prajna.rajendrakumar@...rochip.com>, 
 Conor Dooley <conor.dooley@...rochip.com>, 
 Daire McNamara <daire.mcnamara@...rochip.com>, 
 linux-riscv@...ts.infradead.org, linux-spi@...r.kernel.org, 
 Lukas Bulwahn <lbulwahn@...hat.com>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Lukas Bulwahn <lukas.bulwahn@...hat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file entry in RISC-V MICROCHIP
 SUPPORT

On Mon, 17 Nov 2025 11:40:44 +0100, Lukas Bulwahn wrote:
> Commit 71c814e98696 ("spi: microchip: rename driver file and internal
> identifiers") renames spi-microchip-core.c to spi-mpfs.c, but misses to
> adjust the file entry in RISC-V MICROCHIP SUPPORT.
> 
> Adjust the file entry after this renaming.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: adjust file entry in RISC-V MICROCHIP SUPPORT
      commit: bd79452b39c21599e2cff42e9fbeb182656b6f6a

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