From: Mike Christie <michaelc@cs.wisc.edu>
To: linux-scsi@vger.kernel.org
Subject: Re: iscsi update for scsi-post
Date: Wed, 24 Sep 2008 11:49:11 -0500 [thread overview]
Message-ID: <48DA6F87.6020008@cs.wisc.edu> (raw)
In-Reply-To: <1222274775-8834-1-git-send-email-michaelc@cs.wisc.edu>
michaelc@cs.wisc.edu wrote:
> The following patches are fixes and enhancements for 2.6.28 scsi-post,
I meant the 2.6.28 feature window. The patches are made over scsi-post
instead of scsi-misc because of the new DID_TRANSPORT error patches,
Sorry about the bad wording.
> becuase:
>
> Subject: [PATCH 6/7] libiscsi: check reason why we are stopping iscsi session to determine error value
>
> collides with other patches in that tree.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-09-24 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 16:46 iscsi update for scsi-post michaelc
2008-09-24 16:46 ` [PATCH 1/7] libiscsi: fix data corruption when target has to resend data-in packets michaelc
2008-09-24 16:46 ` [PATCH 2/7] libiscsi: Support drivers initiating session removal michaelc
2008-09-24 16:46 ` [PATCH 3/7] iscsi class: fix endpoint id handling michaelc
2008-09-24 16:46 ` [PATCH 4/7] libiscsi: rename host reset to target reset michaelc
2008-09-24 16:46 ` [PATCH 5/7] iscsi_tcp: return a descriptive error value during connection errors michaelc
2008-09-24 16:46 ` [PATCH 6/7] libiscsi: check reason why we are stopping iscsi session to determine error value michaelc
2008-09-24 16:46 ` [PATCH 7/7] libiscsi: fix locking in iscsi_eh_device_reset michaelc
2008-09-24 16:49 ` Mike Christie [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=48DA6F87.6020008@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox