linux-kernel - Re: [PATCH 0/5] Some bug fix for lpspi

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]

Date:   Wed, 22 Jul 2020 14:45:22 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Clark Wang <xiaoning.wang@....com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] Some bug fix for lpspi

On Tue, 14 Jul 2020 15:52:46 +0800, Clark Wang wrote:
> This series mainly fixes some recently discovered problems about CS for
> LPSPI module.
> 
> And two patches to improve the reliability of the driver.
> 
> Regards,
> Clark
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: lpspi: fix the imbalance of runtime pm function call
      commit: 2abbae5a0e4e1d81016f56a403b2daadfee314c3
[2/5] spi: lpspi: add NULL check when probe device
      (no commit info)
[3/5] spi: lpspi: fix kernel warning dump when probe fail after calling spi_register
      (no commit info)
[4/5] spi: lpspi: handle EPROBE_DEFER when get cs-gpios number
      (no commit info)
[5/5] spi: lpspi: fix using CS discontinuously on i.MX8DXLEVK
      (no commit info)

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