From: Daejun Park <daejun7.park@samsung.com>
To: "cang@codeaurora.org" <cang@codeaurora.org>
Cc: ALIM AKHTAR <alim.akhtar@samsung.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"hongwus@codeaurora.org" <hongwus@codeaurora.org>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"kernel-team@android.com" <kernel-team@android.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"nguyenb@codeaurora.org" <nguyenb@codeaurora.org>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"sthumma@codeaurora.org" <sthumma@codeaurora.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>,
"ygardi@codeaurora.org" <ygardi@codeaurora.org>
Subject: RE: [PATCH v4 2/2] scsi: ufs: Fix wrong Task Tag used in task management request UPIUs
Date: Thu, 01 Apr 2021 15:44:19 +0900 [thread overview]
Message-ID: <1891546521.01617260402234.JavaMail.epsvc@epcpadp3> (raw)
In-Reply-To: CGME20210401064419epcms2p6b289c9ba573d15883e3e92ddcd233e11@epcms2p6
Hi, Can Guo
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
...
>
> req->end_io_data = &wait;
> - free_slot = req->tag;
> WARN_ON_ONCE(free_slot < 0 || free_slot >= hba->nutmrs);
I think this line should be removed.
Thanks,
Daejun
next parent reply other threads:[~2021-04-01 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210401064419epcms2p6b289c9ba573d15883e3e92ddcd233e11@epcms2p6>
2021-04-01 6:44 ` Daejun Park [this message]
2021-04-01 7:17 ` [PATCH v4 2/2] scsi: ufs: Fix wrong Task Tag used in task management request UPIUs Can Guo
[not found] <1617166236-39908-1-git-send-email-cang@codeaurora.org>
2021-03-31 4:50 ` Can Guo
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=1891546521.01617260402234.JavaMail.epsvc@epcpadp3 \
--to=daejun7.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=cang@codeaurora.org \
--cc=hongwus@codeaurora.org \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=stanley.chu@mediatek.com \
--cc=sthumma@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=ygardi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).