Message ID | 20220610074459.3261383-1-andy.chiu@sifive.com (mailing list archive) |
---|---|
Headers | show |
Series | Add simple PM operations to sifive-spi | expand |
On Fri, Jun 10, 2022 at 03:44:58PM +0800, Andy Chiu wrote: > The patch has been tested on Unmatched using pm_test. The Unmatched board > uses SD over SPI and it was tested by initiating S2RAM cycles for all > devices while reading/writing files at the same time. We found no dropped > connection to the card or corrupted filesystem during test cycles. Please don't send cover letters for single patches, if there is anything that needs saying put it in the changelog of the patch or after the --- if it's administrative stuff. This reduces mail volume and ensures that any important information is recorded in the changelog rather than being lost.
On Fri, 10 Jun 2022 15:44:58 +0800, Andy Chiu wrote: > The patch has been tested on Unmatched using pm_test. The Unmatched board > uses SD over SPI and it was tested by initiating S2RAM cycles for all > devices while reading/writing files at the same time. We found no dropped > connection to the card or corrupted filesystem during test cycles. > > Andy Chiu (1): > spi: sifive: add PM callbacks to support suspend/resume > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: sifive: add PM callbacks to support suspend/resume commit: a1f0161eadbd7941c09b5f4c6a210c390d2b86d6 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