linux-kernel - Re: [PATCH] spi: spi-mt65xx: Use threaded interrupt for non-SPIMEM transfer

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172226760809.71144.14726035193284084228.b4-ty@kernel.org>
Date: Mon, 29 Jul 2024 16:40:08 +0100
From: Mark Brown <broonie@...nel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: matthias.bgg@...il.com, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-mediatek@...ts.infradead.org, kernel@...labora.com
Subject: Re: [PATCH] spi: spi-mt65xx: Use threaded interrupt for non-SPIMEM
 transfer

On Fri, 26 Jul 2024 13:47:21 +0200, AngeloGioacchino Del Regno wrote:
> In order to avoid blocking for an excessive amount of time, eventually
> impacting on system responsiveness, interrupt handlers should finish
> executing in as little time as possible.
> 
> Use threaded interrupt and move the SPI transfer handling (both
> CPU and DMA) for the non-spimem case to an interrupt thread instead.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-mt65xx: Use threaded interrupt for non-SPIMEM transfer
      commit: 5972eb05ca322bb1efe44d32808bc7a331e7aee4

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