From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
Bean Huo <huobean@gmail.com>, Avri Altman <avri.altman@wdc.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Can Guo <cang@codeaurora.org>,
Asutosh Das <asutoshd@codeaurora.org>,
Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/2] scsi: ufs: Do not exit reset of error functions unless operational
Date: Mon, 04 Oct 2021 22:21:14 -0400 [thread overview]
Message-ID: <yq1fstg8b5b.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20211002154550.128511-1-adrian.hunter@intel.com> (Adrian Hunter's message of "Sat, 2 Oct 2021 18:45:48 +0300")
Adrian,
> Callers of ufshcd_reset_and_restore() and ufshcd_err_handler() expect
> them to return in an operational state. However, the code does not
> check the state before exiting. Here are a couple of patches to
> correct that.
Applied to 5.16/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-10-05 2:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 15:45 [PATCH 0/2] scsi: ufs: Do not exit reset of error functions unless operational Adrian Hunter
2021-10-02 15:45 ` [PATCH 1/2] scsi: ufs: Do not exit ufshcd_reset_and_restore() unless operational or dead Adrian Hunter
2021-10-03 7:26 ` Avri Altman
2021-10-02 15:45 ` [PATCH 2/2] scsi: ufs: Do not exit ufshcd_err_handler() " Adrian Hunter
2021-10-03 6:47 ` Avri Altman
2021-10-03 7:10 ` Adrian Hunter
2021-10-03 7:25 ` Avri Altman
2021-10-03 7:26 ` Avri Altman
2021-10-05 2:21 ` Martin K. Petersen [this message]
2021-10-12 20:35 ` [PATCH 0/2] scsi: ufs: Do not exit reset of error functions unless operational 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=yq1fstg8b5b.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox