[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174622450030.4079756.4548805140553254933.b4-ty@kernel.org>
Date: Sat, 03 May 2025 07:21:40 +0900
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Mason Zhang <Mason.Zhang@...iatek.com>, Aaron Kling <webgeek1234@...il.com>
Cc: linux-spi@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] spi: tegra114: Don't fail set_cs_timing when delays
are zero
On Wed, 23 Apr 2025 21:03:03 -0500, Aaron Kling wrote:
> The original code would skip null delay pointers, but when the pointers
> were converted to point within the spi_device struct, the check was not
> updated to skip delays of zero. Hence all spi devices that didn't set
> delays would fail to probe.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: tegra114: Don't fail set_cs_timing when delays are zero
commit: 4426e6b4ecf632bb75d973051e1179b8bfac2320
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
Powered by blists - more mailing lists