linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Andy Chiu <andy.chiu@sifive.com>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
	linux-spi@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH next 0/1] Add simple PM operations to sifive-spi
Date: Fri, 10 Jun 2022 13:05:06 +0100	[thread overview]
Message-ID: <YqMzcn9/otXYDdin@sirena.org.uk> (raw)
In-Reply-To: <20220610074459.3261383-1-andy.chiu@sifive.com>

[-- Attachment #1: Type: text/plain, Size: 663 bytes --]

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. 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-06-10 12:05 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 ` Mark Brown [this message]
2022-06-10 15:59 ` [PATCH next 0/1] Add simple PM operations to sifive-spi Mark Brown

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=YqMzcn9/otXYDdin@sirena.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).