linux-kernel - Re: [PATCH] spi: spi-fsl-dspi: Revert unintended dependency change in config SPI_FSL

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: <175009082316.296200.2676929998940689118.b4-ty@kernel.org>
Date: Mon, 16 Jun 2025 17:20:23 +0100
From: Mark Brown <broonie@...nel.org>
To: James Clark <james.clark@...aro.org>, 
 Ciprian Marian Costea <ciprianmarian.costea@....com>, 
 Larisa Grigore <Larisa.Grigore@....com>, 
 Stoica Cosmin-Stefan <cosmin.stoica@....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] spi: spi-fsl-dspi: Revert unintended dependency change
 in config SPI_FSL_DSPI

On Mon, 16 Jun 2025 11:19:55 +0200, Lukas Bulwahn wrote:
> Commit 9a30e332c36c ("spi: spi-fsl-dspi: Enable support for S32G
> platforms") reworks the dependencies of config SPI_FSL_DSPI, but introduces
> a typo changing the dependency to M5441x to a dependency on a non-existing
> config M54541x.
> 
> Revert the unintended change to depend on the config M5441x.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-fsl-dspi: Revert unintended dependency change in config SPI_FSL_DSPI
      commit: dce4bc30f42d313b4dc5832316196411b7f07ad0

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