linux-kernel - Re: [PATCH] spi: atmel-quadspi: Disable the QSPI IP at suspend()

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

Message-Id: <161305799890.12648.15037245423068627644.b4-ty@kernel.org>
Date:   Thu, 11 Feb 2021 15:39:58 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Tudor Ambarus <tudor.ambarus@...rochip.com>
Cc:     linux-kernel@...r.kernel.org, alexandre.belloni@...tlin.com,
        linux-spi@...r.kernel.org, ludovic.desroches@...rochip.com,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] spi: atmel-quadspi: Disable the QSPI IP at suspend()

On Wed, 10 Feb 2021 15:54:28 +0200, Tudor Ambarus wrote:
> It is safer to disable the QSPI IP at suspend, in order to avoid
> possible impact of glitches on the internal FSMs. This is a theoretical
> fix, there were no problems seen as of now. Tested on sama5d2 and
> sam9x60 versions of the IP.

Applied to

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

Thanks!

[1/1] spi: atmel-quadspi: Disable the QSPI IP at suspend()
      commit: df6978b7ea6349eb32078c42b917559f5510aebd

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