From: Jeff Garzik <jeff@garzik.org>
To: Ramya Desai <ramya.desai@gmail.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Alan Stern <stern@rowland.harvard.edu>,
USB list <linux-usb@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: Return of PENDING status to SCSI driver
Date: Mon, 15 Jun 2009 13:19:08 -0400 [thread overview]
Message-ID: <4A36828C.1020506@garzik.org> (raw)
In-Reply-To: <3e7aae30906150742l18e74a8fua5f08686c2c76454@mail.gmail.com>
Ramya Desai wrote:
> I can not post the code in public because of some limitations I have.
> But Still I am confused with return status (to SCSI layer) for the
> command while it is in progress, to get the next command. Is it some
> thing like PENDING?
To repeat: any "return status" of a currently-executing command is
largely irrelevant to you.
1) You are given a command, via ->queuecommand
2) You send that command to hardware
3) When hardware is done, call the completion callback
Your driver never returns a "pending" status to the SCSI layer. The
SCSI layer is __already__ fully aware that a command is pending, when it
is passed to your driver.
Jeff
next prev parent reply other threads:[~2009-06-15 17:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 9:29 Return of PENDING status to SCSI driver Ramya Desai
2009-06-12 11:32 ` Jeff Garzik
2009-06-12 12:54 ` Ramya Desai
2009-06-12 17:26 ` Stefan Richter
2009-06-14 9:16 ` Boaz Harrosh
2009-06-15 12:07 ` Ramya Desai
2009-06-15 12:26 ` Matthew Wilcox
2009-06-15 12:29 ` Boaz Harrosh
[not found] ` <4A363EB4.8000102-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2009-06-15 14:01 ` Alan Stern
2009-06-15 14:07 ` Ramya Desai
[not found] ` <3e7aae30906150707we781237o366950971d748b6f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-15 14:33 ` Boaz Harrosh
2009-06-15 14:42 ` Ramya Desai
[not found] ` <3e7aae30906150742l18e74a8fua5f08686c2c76454-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-15 14:50 ` Ramya Desai
[not found] ` <3e7aae30906150750m6809aa87v35f739e0a72243d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-15 14:59 ` Matthew Dharm
2009-06-15 14:59 ` Alan Stern
2009-06-15 16:31 ` Boaz Harrosh
[not found] ` <4A36776C.5010208-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2009-06-16 13:35 ` Ramya Desai
2009-06-16 13:59 ` Alan Cox
2009-06-16 14:27 ` Boaz Harrosh
2009-06-16 14:39 ` James Bottomley
[not found] ` <4A37ABDC.4050308-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2009-06-16 15:09 ` Ramya Desai
2009-06-16 15:22 ` Alan Stern
[not found] ` <3e7aae30906160809y32f0c8f6j3352cd1ec2bfe34a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-16 15:27 ` Boaz Harrosh
[not found] ` <3e7aae30906160635g4d191a4exdb710554a349cac0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-16 15:13 ` Alan Stern
2009-06-15 17:19 ` Jeff Garzik [this message]
2009-06-15 14:40 ` Alan Stern
2009-06-15 14:42 ` Boaz Harrosh
[not found] ` <4A365DCA.2030907-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2009-06-15 14:49 ` Alan Stern
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=4A36828C.1020506@garzik.org \
--to=jeff@garzik.org \
--cc=bharrosh@panasas.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ramya.desai@gmail.com \
--cc=stern@rowland.harvard.edu \
/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