From: Stanley Chu <stanley.chu@mediatek.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Can Guo <cang@codeaurora.org>, <asutoshd@codeaurora.org>,
<nguyenb@codeaurora.org>, <hongwus@codeaurora.org>,
<rnayak@codeaurora.org>, <linux-scsi@vger.kernel.org>,
<kernel-team@android.com>, <saravanak@google.com>,
<salyzyn@google.com>
Subject: Re: [PATCH V7 0/3] Minor fixes to UFS error handling
Date: Tue, 8 Dec 2020 13:04:10 +0800 [thread overview]
Message-ID: <1607403850.3580.24.camel@mtkswgap22> (raw)
In-Reply-To: <yq1mtyp19en.fsf@ca-mkp.ca.oracle.com>
Hi Martin,
On Mon, 2020-12-07 at 18:31 -0500, Martin K. Petersen wrote:
> Can,
>
> > This series mainly fixes below two things which come along with UFS error
> > handling in some corner cases.
> > [1] Concurrency problems btw err_handler and paths like system suspend/resume/shutdown and async scan.
> > [2] Race condition btw UFS error recovery and task abort which happens to W-LU during suspend/resume/shutdown.
>
> Applied to 5.11/scsi-staging, thanks!
>
> Stanley: Please verify conflict resolution with your event notification
> series.
Conflict is resolved perfectly!
Thanks for your time : )
Stanley Chu
next prev parent reply other threads:[~2020-12-08 5:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 12:04 [PATCH V7 0/3] Minor fixes to UFS error handling Can Guo
2020-12-02 12:04 ` [PATCH V7 1/3] scsi: ufs: Serialize eh_work with system PM events and async scan Can Guo
2020-12-02 12:04 ` [PATCH V7 2/3] scsi: ufs: Fix a race condition between ufshcd_abort and eh_work Can Guo
2020-12-03 2:21 ` Stanley Chu
2020-12-03 4:01 ` Can Guo
2020-12-03 4:51 ` Stanley Chu
2020-12-03 5:11 ` Can Guo
2020-12-03 5:19 ` Stanley Chu
2020-12-03 5:21 ` Can Guo
2020-12-02 12:04 ` [PATCH V7 3/3] scsi: ufs: Print host regs in IRQ handler when AH8 error happens Can Guo
2020-12-07 23:31 ` [PATCH V7 0/3] Minor fixes to UFS error handling Martin K. Petersen
2020-12-08 5:04 ` Stanley Chu [this message]
2020-12-09 17:23 ` 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=1607403850.3580.24.camel@mtkswgap22 \
--to=stanley.chu@mediatek.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=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.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