linux-kernel - Re: [PATCH] MAINTAINERS: repair file entry in AIROHA SPI SNFI DRIVER

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: <171513594308.1998064.12450268139510361452.b4-ty@kernel.org>
Date: Wed, 08 May 2024 11:39:03 +0900
From: Mark Brown <broonie@...nel.org>
To: Lorenzo Bianconi <lorenzo@...nel.org>, Ray Liu <ray.liu@...oha.com>, 
 linux-arm-kernel@...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: repair file entry in AIROHA SPI SNFI
 DRIVER

On Tue, 07 May 2024 16:14:49 +0200, Lukas Bulwahn wrote:
> Commit a403997c1201 ("spi: airoha: add SPI-NAND Flash controller driver")
> adds a new section AIROHA SPI SNFI DRIVER referring to the file
> spi-airoha.c. The commit however adds the file spi-airoha-snfi.c.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: repair file entry in AIROHA SPI SNFI DRIVER
      commit: eab80a2ee46bb362e2c4434cf0da96d3a6bda544

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