linux-kernel - Re: [PATCH v2 0/2] spi: tegra210-quad: Improve messages on pathological case

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: <174474794125.1085405.1696078775184536618.b4-ty@kernel.org>
Date: Tue, 15 Apr 2025 21:12:21 +0100
From: Mark Brown <broonie@...nel.org>
To: Thierry Reding <thierry.reding@...il.com>, 
 Jonathan Hunter <jonathanh@...dia.com>, 
 Sowjanya Komatineni <skomatineni@...dia.com>, 
 Laxman Dewangan <ldewangan@...dia.com>, Breno Leitao <leitao@...ian.org>
Cc: linux-tegra@...r.kernel.org, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, rmikey@...a.com, kernel-team@...a.com
Subject: Re: [PATCH v2 0/2] spi: tegra210-quad: Improve messages on
 pathological case

On Tue, 01 Apr 2025 06:47:48 -0700, Breno Leitao wrote:
> I maintain several hosts with tegra210-quad controllers, some of which
> experience data transmission failures. Debugging these issues has been
> challenging due to excessive log messages from the driver.
> 
> Since these devices do not have a way to reset[1], then we want to avoid
> warning and printing a bunch of messages, otherwise the host will
> overflow the serial. Fix it by:
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: tegra210-quad: use WARN_ON_ONCE instead of WARN_ON for timeouts
      commit: 41c721fc093938745d116c3a21326a0ee03bb491
[2/2] spi: tegra210-quad: add rate limiting and simplify timeout error message
      commit: 21f4314e66ed8d40b2ee24185d1a06a07a512eb1

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