linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Reed <mdr@sgi.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	"Moore, Eric Dean" <Eric.Moore@lsil.com>
Subject: [REPOST][PATCH 0/6] mpt fusion - fibre channel updates / bug fixes
Date: Wed, 24 May 2006 15:06:38 -0500	[thread overview]
Message-ID: <4474BCCE.8010009@sgi.com> (raw)

If possible, 2.6.17.  (Well, I can dream....)

Bugs fixed:

	* fibre channel target discovery prematurely terminates
	* fix infinite request/response loop during board reset
	* interrupting board reset with ctrl-c can leave board
	  unusable, requiring reboot to recover

Code reorg:

	* move fibre channel event and reset handling to mptfc
	  (better isolates future changes to this module)

Bug fix / feature: (depends upon point of view)

	* Set firmware target missing timers to one second so that
	  the transport's dev loss timer is more quickly started


                 reply	other threads:[~2006-05-24 20:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4474BCCE.8010009@sgi.com \
    --to=mdr@sgi.com \
    --cc=Eric.Moore@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --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;
as well as URLs for NNTP newsgroup(s).