From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Jack Wang <jinpu.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>,
Sebastian Riemer
<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] IB/srp: add change_queue_depth and change_queue_type support
Date: Tue, 27 Aug 2013 18:46:09 +0200 [thread overview]
Message-ID: <521CD7D1.9000807@acm.org> (raw)
In-Reply-To: <521CD628.8090902-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
On 08/27/13 18:39, Jack Wang wrote:
> I look into scsi core about above statement:
> In drivers/scsi/scsi_scan.c:865:
>
> if ((sdev->scsi_level >= SCSI_2) && (inq_result[7] & 2) &&
> !(*bflags & BLIST_NOTQ))
> sdev->tagged_supported = 1;
> It check inquiry result byte 7 with cmdque bit.
Ah, thanks for looking that up. I had overlooked that statement. So it
should be fine to keep all the code that depends on the value of
sdev->tagged_supported.
Regards,
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-08-27 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 13:53 [PATCH] IB/srp: add change_queue_depth and change_queue_type support Jack Wang
[not found] ` <521B5DD5.3020804-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-08-27 8:31 ` Bart Van Assche
[not found] ` <521C63FA.3070709-HInyCGIudOg@public.gmane.org>
2013-08-27 9:06 ` Jack Wang
2013-08-27 16:39 ` Jack Wang
[not found] ` <521CD628.8090902-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-08-27 16:46 ` Bart Van Assche [this message]
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=521CD7D1.9000807@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org \
--cc=jinpu.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.