linux-kernel - Re: [PATCH] MAINTAINERS: adjust the file entry in SPI OFFLOAD

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: <173991423052.1713526.6394807497548942772.b4-ty@kernel.org>
Date: Tue, 18 Feb 2025 21:30:30 +0000
From: Mark Brown <broonie@...nel.org>
To: David Lechner <dlechner@...libre.com>, 
 Jonathan Cameron <Jonathan.Cameron@...wei.com>, 
 Nuno Sa <nuno.sa@...log.com>, 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 the file entry in SPI OFFLOAD

On Mon, 17 Feb 2025 10:28:51 +0100, Lukas Bulwahn wrote:
> Commit 8e02d1886988 ("spi: add basic support for SPI offloading") adds a
> new MAINTAINERS section referring to the non-existent file
> include/linux/spi/spi-offload.h rather than referring to the files added
> with this commit in the directory include/linux/spi/offload/.
> 
> Adjust the file reference to the intended directory.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: adjust the file entry in SPI OFFLOAD
      commit: d1a09c610027e446ed30c21f61c2f2443bf92a3f

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