linux-kernel - Re: [PATCH] spi: zynqmp-gqspi: Scale timeout by data size

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: <172356165412.69018.3689361849577189863.b4-ty@kernel.org>
Date: Tue, 13 Aug 2024 16:07:34 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Sean Anderson <sean.anderson@...ux.dev>
Cc: linux-arm-kernel@...ts.infradead.org, 
 Michal Simek <michal.simek@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: zynqmp-gqspi: Scale timeout by data size

On Fri, 09 Aug 2024 16:15:39 -0400, Sean Anderson wrote:
> Large blocks of data time out when reading because we don't wait long
> enough for the transfer to complete. Scale our timeouts based on the
> amount of data we are tranferring, with a healthy dose of pessimism.
> 
> 

Applied to

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

Thanks!

[1/1] spi: zynqmp-gqspi: Scale timeout by data size
      commit: 5d61841c74db8b5bbbf9403f1bd4879f614617d2

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