From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: "'Bart Van Assche'" <bvanassche@acm.org>,
<linux-scsi@vger.kernel.org>, <sc.suh@samsung.com>,
<hy50.seo@samsung.com>, <sh425.lee@samsung.com>,
<bhoon95.kim@samsung.com>, <vkumar.1997@samsung.com>
Subject: RE: [PATCH v1] scsi: ufs: use an generic error code in ufshcd_set_dev_pwr_mode
Date: Thu, 20 Jan 2022 11:51:27 +0900 [thread overview]
Message-ID: <000001d80da8$9e987cd0$dbc97670$@samsung.com> (raw)
In-Reply-To: <3bb0f5ad-2cea-2509-a9e1-d8ed159bd875@acm.org>
> > @@ -8669,6 +8669,7 @@ static int ufshcd_set_dev_pwr_mode(struct ufs_hba
> *hba,
> > pwr_mode, ret);
> > if (ret > 0 && scsi_sense_valid(&sshdr))
> > scsi_print_sense_hdr(sdp, NULL, &sshdr);
> > + ret = -EIO;
> > }
> >
> > if (!ret)
>
> Shouldn't "ret = -EIO" only be executed if ret > 0? Additionally, please
> update the documentation of ufshcd_set_dev_pwr_mode(). I'm referring to
> the following comment: "Returns non-zero if failed to set the requested
> power mode".
>
> Thanks,
>
> Bart.
scsi_execute returns cmd->result(int type) but I think there is no case that the valaue is negative
because all values defined for its most significant byte, i.e. driver byte, are smaller than 0x80.
And I understand the 'ret > 0' presents that something wrong happens during the process.
So I'm not sure if 'ret = -EIO;' should be executed under 'ret > 0'.
--
#define DRIVER_BUSY 0x01
#define DRIVER_SOFT 0x02
And for the comment, I got it.
Thanks
Kiwoong
next prev parent reply other threads:[~2022-01-20 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220117103107epcas2p3d7223ff63f6cb575316695cc8fb155a4@epcas2p3.samsung.com>
2022-01-17 10:29 ` [PATCH v1] scsi: ufs: use an generic error code in ufshcd_set_dev_pwr_mode Kiwoong Kim
2022-01-19 0:45 ` Bart Van Assche
2022-01-20 2:51 ` Kiwoong Kim [this message]
2022-01-20 17:57 ` Bart Van Assche
2022-01-21 5:34 ` 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='000001d80da8$9e987cd0$dbc97670$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=bhoon95.kim@samsung.com \
--cc=bvanassche@acm.org \
--cc=hy50.seo@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@samsung.com \
--cc=vkumar.1997@samsung.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