From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-scsi@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
John Garry <john.garry@huawei.com>,
ericspero@icloud.com, jason600.groome@gmail.com
Subject: Re: [PATCH 3/3] scsi: sd: Rework asynchronous resume support
Date: Thu, 30 Jun 2022 09:09:32 -0700 [thread overview]
Message-ID: <0c498a20-5410-77e5-4492-fcd5fdbfab52@acm.org> (raw)
In-Reply-To: <64551444-39fd-2853-7ea8-053d023df75d@suse.de>
On 6/28/22 23:02, Hannes Reinecke wrote:
> On 6/29/22 00:21, Bart Van Assche wrote:
>> +/* Process sense data after a START command finished. */
>> +static void sd_start_done_work(struct work_struct *work)
>> +{
>> + struct scsi_disk *sdkp = container_of(work, typeof(*sdkp),
>> + start_done_work);
>> + struct scsi_sense_hdr sshdr;
>> + int res = sdkp->start_result;
>> +
>> + if (res == 0)
>> + return;
>> +
>> + sd_print_result(sdkp, "Start/Stop Unit failed", res);
>
> Surely START/STOP unit can succeed, no?
Yes, hence the "if (res == 0) return;" code. Did I perhaps misunderstand
your question?
Bart.
next prev parent reply other threads:[~2022-06-30 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 22:21 [PATCH 0/3] Reduce ATA disk resume time Bart Van Assche
2022-06-28 22:21 ` [PATCH 1/3] scsi: core: Move the definition of SCSI_QUEUE_DELAY Bart Van Assche
2022-06-28 22:21 ` [PATCH 2/3] scsi: core: Retry after a delay if the device is becoming ready Bart Van Assche
2022-06-29 1:21 ` Ming Lei
2022-06-29 22:06 ` Bart Van Assche
2022-06-28 22:21 ` [PATCH 3/3] scsi: sd: Rework asynchronous resume support Bart Van Assche
2022-06-29 6:02 ` Hannes Reinecke
2022-06-30 16:09 ` Bart Van Assche [this message]
2022-06-30 16:23 ` John Garry
2022-06-30 18:57 ` Bart Van Assche
2022-06-30 19:28 ` Bart Van Assche
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=0c498a20-5410-77e5-4492-fcd5fdbfab52@acm.org \
--to=bvanassche@acm.org \
--cc=ericspero@icloud.com \
--cc=hare@suse.de \
--cc=jaegeuk@kernel.org \
--cc=jason600.groome@gmail.com \
--cc=john.garry@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).