linux-kernel - Re: [PATCH] spi: davinci: Adapt transfer's timeout to transfer's length

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: <172486262889.93098.17891332820401670505.b4-ty@kernel.org>
Date: Wed, 28 Aug 2024 17:30:28 +0100
From: Mark Brown <broonie@...nel.org>
To: Bastien Curutchet <bastien.curutchet@...tlin.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 Herve Codina <herve.codina@...tlin.com>, 
 Christopher Cordahi <christophercordahi@...ometrics.ca>
Subject: Re: [PATCH] spi: davinci: Adapt transfer's timeout to transfer's
 length

On Wed, 28 Aug 2024 08:31:31 +0200, Bastien Curutchet wrote:
> The timeout used when waiting for transfer's completion is always set to
> HZ. This isn't enough if a transfer is too large or if the bus speed is
> too low.
> 
> Use the bus speed and the transfer length to calculate an appropriate
> timeout
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: davinci: Adapt transfer's timeout to transfer's length
      commit: 2fe6102bf01a5f4f48f211c2e5c8a274342fccb1

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