linux-kernel - Re: [PATCH v3] spi: cadence: revert "Add SPI transfer delays"

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: <170189669207.80266.3758979779470758907.b4-ty@kernel.org>
Date:   Wed, 06 Dec 2023 21:04:52 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        daniel@...que.org, Nam Cao <namcao@...utronix.de>
Subject: Re: [PATCH v3] spi: cadence: revert "Add SPI transfer delays"

On Wed, 06 Dec 2023 15:52:33 +0100, Nam Cao wrote:
> The commit 855a40cd8ccc ("spi: cadence: Add SPI transfer delays") adds a
> delay after each transfer into the driver's transfer_one(). However,
> the delay is already done in SPI core. So this commit unnecessarily
> doubles the delay amount. Revert this commit.
> 
> 

Applied to

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

Thanks!

[1/1] spi: cadence: revert "Add SPI transfer delays"
      commit: 7a733e060bd20edb63b1f27f0b29cf9b184e0e8b

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