From: Bart Van Assche <bvanassche@acm.org>
To: Adrian Hunter <adrian.hunter@intel.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "James E . J . Bottomley" <jejb@linux.ibm.com>,
Avri Altman <avri.altman@wdc.com>, Bean Huo <huobean@gmail.com>,
Can Guo <cang@codeaurora.org>,
Asutosh Das <asutoshd@codeaurora.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH V2] scsi: ufs: Fix ufshcd_request_sense_async() for Samsung KLUFG8RHDA-B2D1
Date: Mon, 23 Aug 2021 19:27:08 -0700 [thread overview]
Message-ID: <a85f2513-c063-eaf1-ad02-b15a164abbe9@acm.org> (raw)
In-Reply-To: <20210823050117.11608-1-adrian.hunter@intel.com>
On 8/22/21 10:01 PM, Adrian Hunter wrote:
> Samsung KLUFG8RHDA-B2D1 does not clear the unit attention condition if the
> length is zero. So go back to requesting all the sense data, as it was
> before patch "scsi: ufs: Request sense data asynchronously". That is
> simpler than creating and maintaining a quirk for affected devices.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2021-08-24 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 5:01 [PATCH V2] scsi: ufs: Fix ufshcd_request_sense_async() for Samsung KLUFG8RHDA-B2D1 Adrian Hunter
2021-08-24 2:27 ` Bart Van Assche [this message]
2021-08-24 3:34 ` Martin K. Petersen
2021-08-24 11:34 ` Adrian Hunter
2021-08-24 11:41 ` [PATCH V3] " Adrian Hunter
2021-08-25 2:59 ` Martin K. Petersen
2021-08-28 2:31 ` Martin K. Petersen
2021-09-02 10:18 ` [PATCH 0/3] scsi: ufs: Let devices remain runtime suspended during system suspend Adrian Hunter
2021-09-02 10:18 ` [PATCH 1/3] scsi: ufs: Fix error handler clear ua deadlock Adrian Hunter
2021-09-02 16:53 ` Asutosh Das (asd)
2021-09-02 10:18 ` [PATCH 2/3] scsi: ufs: Fix runtime PM dependencies getting broken Adrian Hunter
2021-09-02 10:18 ` [PATCH 3/3] scsi: ufs: Let devices remain runtime suspended during system suspend Adrian Hunter
2021-09-02 17:07 ` Asutosh Das (asd)
2021-09-03 9:55 ` Adrian Hunter
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=a85f2513-c063-eaf1-ad02-b15a164abbe9@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox