From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, andy.chiu@sifive.com,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org,
palmer@dabbelt.com
Subject: Re: [PATCH next 0/1] Add simple PM operations to sifive-spi
Date: Fri, 10 Jun 2022 16:59:04 +0100 [thread overview]
Message-ID: <165487674459.1756526.5750583671148030437.b4-ty@kernel.org> (raw)
In-Reply-To: <20220610074459.3261383-1-andy.chiu@sifive.com>
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-06-10 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 7:44 [PATCH next 0/1] Add simple PM operations to sifive-spi Andy Chiu
2022-06-10 7:44 ` [PATCH next 1/1] spi: sifive: add PM callbacks to support suspend/resume Andy Chiu
2022-06-10 12:04 ` Mark Brown
2022-06-22 3:06 ` Andy Chiu
2022-06-22 10:24 ` Andy Shevchenko
2022-06-10 12:05 ` [PATCH next 0/1] Add simple PM operations to sifive-spi Mark Brown
2022-06-10 15:59 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165487674459.1756526.5750583671148030437.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox