linux-kernel - Re: (subset) [PATCH 0/2] fix the issue when xfer by spi-altera

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <160925239795.47982.14921180945738212657.b4-ty@kernel.org>
Date:   Tue, 29 Dec 2020 14:33:17 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, Xu Yilun <yilun.xu@...el.com>
Cc:     matthew.gerlach@...ux.intel.com, linux-kernel@...r.kernel.org,
        lgoncalv@...hat.com, trix@...hat.com, russell.h.weight@...el.com,
        hao.wu@...el.com
Subject: Re: (subset) [PATCH 0/2] fix the issue when xfer by spi-altera

On Tue, 29 Dec 2020 13:27:40 +0800, Xu Yilun wrote:
> When doing spi xfer by spi-altera, divide by 0 exception happens in
> spi_transfer_wait(), This is because the xfer->speed_hz is always
> clamped to 0 by spi->controller->max_speed_hz, the feature is
> introduced in:
> 
> commit 9326e4f1e5dd ("spi: Limit the spi device max speed to controller's max speed")
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: altera: fix return value for altera_spi_txrx()
      commit: ede090f5a438e97d0586f64067bbb956e30a2a31

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