[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <17db01dc1ba6$41d37350$c57a59f0$@samsung.com>
Date: Tue, 2 Sep 2025 10:09:39 +0900
From: "DooHyun Hwang" <dh0421.hwang@...sung.com>
To: "'Bart Van Assche'" <bvanassche@....org>, <linux-scsi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <alim.akhtar@...sung.com>,
<avri.altman@....com>, <James.Bottomley@...senPartnership.com>,
<martin.petersen@...cle.com>, <peter.wang@...iatek.com>,
<manivannan.sadhasivam@...aro.org>, <quic_mnaresh@...cinc.com>
Cc: <grant.jung@...sung.com>, <jt77.jang@...sung.com>,
<junwoo80.lee@...sung.com>, <jangsub.yi@...sung.com>,
<sh043.lee@...sung.com>, <cw9316.lee@...sung.com>,
<sh8267.baek@...sung.com>, <wkon.kim@...sung.com>
Subject: RE: [PATCH 1/2] scsi: ufs: Add an enum for ufs_trace to check ufs
cmd error
On 9/1/25 7:4 AM, Bart Van Assche wrote:
> On 8/31/25 6:31 PM, DooHyun Hwang wrote:
> > UFS_CMD_ERR stands for "completion error".
>
> No it doesn't. In the UFS driver and also in many other driver "cmd"
> stands for "command" and not for "completion". Please change the
> "UFS_CMD_ERR" enum label.
>
> Bart.
I'm sorry. There was a misunderstanding in my previous comment.
The UFS_CMD_ERR stands for "command completion error."
I wanted to make it consistent with the other enums.
For example, query errors are defined as UFS_QUERY_ERR,
and Task Management errors are defined as UFS_TM_ERR.
I hope to use UFS_CMD_ERR for the same classification purposes
as UFS_CMD_SEND or UFS_CMD_COMP.
Therefore, UFS_CMD_ERR can be used for logging SCSI or UIC commands.
Thank you.
DooHyun Hwang.
Powered by blists - more mailing lists