From: Kiwoong Kim <kwmad.kim@samsung.com>
To: adrian.hunter@intel.com
Cc: alim.akhtar@samsung.com, asutoshd@codeaurora.org,
avri.altman@wdc.com, bvanassche@acm.org, cang@codeaurora.org,
huobean@gmail.com, jejb@linux.ibm.com,
linux-scsi@vger.kernel.org, liwei213@huawei.com,
manivannan.sadhasivam@linaro.org, martin.petersen@oracle.com,
Kiwoong Kim <kwmad.kim@samsung.com>
Subject: Re: [PATCH V5 1/3] scsi: ufs: Fix error handler clear ua deadlock
Date: Tue, 28 Sep 2021 15:55:20 +0900 [thread overview]
Message-ID: <1632812120-27857-1-git-send-email-kwmad.kim@samsung.com> (raw)
In-Reply-To: <20210922093842.18025-2-adrian.hunter@intel.com>
> +static int ufshcd_request_sense_direct(struct ufs_hba *hba, u8 wlun)
..
How about using ufshcd_compose_dev_cmd w/ modifying the function,
ufshcd_prepare_utp_scsi_cmd_upiu and something ? I think it can be made
w/ small changes. And for prdt, it seems to be good because it's tiny.
next prev parent reply other threads:[~2021-09-28 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 9:38 [PATCH V5 0/3] scsi: ufs: Let devices remain runtime suspended during system suspend Adrian Hunter
2021-09-22 9:38 ` [PATCH V5 1/3] scsi: ufs: Fix error handler clear ua deadlock Adrian Hunter
[not found] ` <CGME20210928071133epcas2p28e00e20bbebbb5c1920933204f91743b@epcas2p2.samsung.com>
2021-09-28 6:55 ` Kiwoong Kim [this message]
2021-09-30 12:44 ` Adrian Hunter
[not found] ` <CGME20210929051745epcas2p1024eb171d57dca361d2d3d522683770d@epcas2p1.samsung.com>
2021-09-29 5:01 ` Kiwoong Kim
2021-09-30 12:43 ` Adrian Hunter
2021-09-22 9:38 ` [PATCH V5 2/3] scsi: ufs: Fix runtime PM dependencies getting broken Adrian Hunter
2021-09-22 9:38 ` [PATCH V5 3/3] scsi: ufs: Let devices remain runtime suspended during system suspend Adrian Hunter
2021-09-22 16:15 ` Asutosh Das (asd)
[not found] <CGME20210928064756epcas2p3975b89e0cecd0ca1807b354bafadccd3@epcas2p3.samsung.com>
2021-09-28 6:47 ` [PATCH V5 1/3] scsi: ufs: Fix error handler clear ua deadlock Kiwoong Kim
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=1632812120-27857-1-git-send-email-kwmad.kim@samsung.com \
--to=kwmad.kim@samsung.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 \
--cc=liwei213@huawei.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.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 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.