mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>,
	 Jonathan Hunter <jonathanh@nvidia.com>,
	 Sowjanya Komatineni <skomatineni@nvidia.com>,
	 Laxman Dewangan <ldewangan@nvidia.com>,
	Breno Leitao <leitao@debian.org>
Cc: linux-tegra@vger.kernel.org, linux-spi@vger.kernel.org,
	 linux-kernel@vger.kernel.org, rmikey@meta.com,
	kernel-team@meta.com
Subject: Re: [PATCH v2 0/2] spi: tegra210-quad: Improve messages on pathological case
Date: Tue, 15 Apr 2025 21:12:21 +0100	[thread overview]
Message-ID: <174474794125.1085405.1696078775184536618.b4-ty@kernel.org> (raw)
In-Reply-To: <20250401-tegra-v2-0-126c293ec047@debian.org>

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


      parent reply	other threads:[~2025-04-15 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 13:47 Breno Leitao
2025-04-01 13:47 ` [PATCH v2 1/2] spi: tegra210-quad: use WARN_ON_ONCE instead of WARN_ON for timeouts Breno Leitao
2025-04-01 13:47 ` [PATCH v2 2/2] spi: tegra210-quad: add rate limiting and simplify timeout error message Breno Leitao
2025-04-15 20:12 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=174474794125.1085405.1696078775184536618.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-team@meta.com \
    --cc=ldewangan@nvidia.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rmikey@meta.com \
    --cc=skomatineni@nvidia.com \
    --cc=thierry.reding@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®