From: James Smart <James.Smart@Emulex.Com>
To: michaelc@cs.wisc.edu
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] iscsi class, qla4xxx and libiscsi: export iscsi session state in sysfs
Date: Thu, 15 Mar 2007 08:58:50 -0400 [thread overview]
Message-ID: <45F9430A.9010309@emulex.com> (raw)
In-Reply-To: <11739019693216-git-send-email-michaelc@cs.wisc.edu>
> @@ -1768,7 +1781,8 @@ static void iscsi_start_session_recovery
> * flush queues.
> */
> spin_lock_bh(&session->lock);
> - fail_all_commands(conn);
> + fail_all_commands(conn,
> + STOP_CONN_RECOVER ? DID_BUS_BUSY : DID_ERROR);
> flush_control_queues(session, conn);
> spin_unlock_bh(&session->lock);
>
I'm assuming you do not support error recovery level 2, right ?
> +int iscsi_session_chkready(struct iscsi_cls_session *session)
...
> +EXPORT_SYMBOL_GPL(iscsi_session_chkready);
Any reason this isn't an inline ?
next prev parent reply other threads:[~2007-03-15 12:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 19:52 RFC: add transport host byte values and common failure behavior michaelc
2007-03-14 19:52 ` [PATCH 1/4] iscsi class, qla4xxx and libiscsi: export iscsi session state in sysfs michaelc
2007-03-14 19:52 ` [PATCH 2/4] scsi: add transport host byte errors michaelc
2007-03-14 19:52 ` [PATCH 3/4] iscsi class, libiscsi and qla4xxx: convert to new transport host byte values michaelc
2007-03-14 19:52 ` [PATCH 4/4] fc class: use " michaelc
2007-03-14 20:11 ` [PATCH 2/4] scsi: add transport host byte errors Mike Christie
2007-03-14 21:14 ` Mike Christie
2007-03-15 13:41 ` [PATCH 4/4] fc class: use transport host byte values James Smart
2007-03-15 14:26 ` Mike Christie
2007-03-15 14:45 ` James Smart
2007-03-15 13:20 ` [PATCH 2/4] scsi: add transport host byte errors James Smart
2007-03-15 14:52 ` Mike Christie
2007-03-15 16:33 ` James Smart
2007-03-15 12:58 ` James Smart [this message]
2007-03-15 14:20 ` [PATCH 1/4] iscsi class, qla4xxx and libiscsi: export iscsi session state in sysfs Mike Christie
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=45F9430A.9010309@emulex.com \
--to=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.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;
as well as URLs for NNTP newsgroup(s).