From: Daejun Park <daejun7.park@samsung.com>
To: "asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"ziqichen@codeaurora.org" <ziqichen@codeaurora.org>,
"nguyenb@codeaurora.org" <nguyenb@codeaurora.org>,
"hongwus@codeaurora.org" <hongwus@codeaurora.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"kernel-team@android.com" <kernel-team@android.com>,
"cang@codeaurora.org" <cang@codeaurora.org>
Subject: RE: [PATCH v2 0/3] Three minor fixes w.r.t suspend/resume
Date: Mon, 26 Apr 2021 14:47:49 +0900 [thread overview]
Message-ID: <20210426054749epcms2p27a2f08f34d07a6754d62c03b125ed632@epcms2p2> (raw)
In-Reply-To: <1619408921-30426-1-git-send-email-cang@codeaurora.org>
Hi Can Guo,
>1st change can fix a possible OCP issue when AH8 error happens.
>2nd and 3rd change can fix race conditions btw suspend/resume and other contexts.
>
>Can Guo (3):
> scsi: ufs: Do not put UFS power into LPM if link is broken
> scsi: ufs: Cancel rpm_dev_flush_recheck_work during system suspend
> scsi: ufs: Narrow down fast pass in system suspend path
>
>Change since V1:
>- Incorporated Daejun's comment.
>
> drivers/scsi/ufs/ufshcd.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
This series looks good to me.
Reviewed-by: Daejun Park <daejun7.park@samsung.com>
Thanks,
Daejun
next prev parent reply other threads:[~2021-04-26 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 3:48 [PATCH v2 0/3] Three minor fixes w.r.t suspend/resume Can Guo
2021-04-26 3:48 ` [PATCH v2 1/3] scsi: ufs: Do not put UFS power into LPM if link is broken Can Guo
2021-04-26 3:48 ` [PATCH v2 2/3] scsi: ufs: Cancel rpm_dev_flush_recheck_work during system suspend Can Guo
2021-04-26 3:48 ` [PATCH v2 3/3] scsi: ufs: Narrow down fast pass in system suspend path Can Guo
[not found] ` <CGME20210426034911epcas2p12dc728215c9a56e3dd2a7870f63e107b@epcms2p2>
2021-04-26 5:47 ` Daejun Park [this message]
2021-04-29 3:18 ` [PATCH v2 0/3] Three minor fixes w.r.t suspend/resume Martin K. Petersen
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=20210426054749epcms2p27a2f08f34d07a6754d62c03b125ed632@epcms2p2 \
--to=daejun7.park@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=hongwus@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nguyenb@codeaurora.org \
--cc=ziqichen@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.