public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: Problem Adding Transport Class support to fusion
Date: Tue, 31 May 2005 12:40:55 -0500	[thread overview]
Message-ID: <1117561255.4952.14.camel@mulgrave> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C028C57FA@nacos172.co.lsil.com>

Well ... I seem to have got parameter getting and setting working just
about OK (modulo a few coupling issues).

The fusion driver seems to have quite a big event subsystem.  Is there
an event that will report a device transfer agreement change? (without
this it's a bit difficult to keep track of where the device and the
fusion core are with negotiation)

Thanks,

James



  parent reply	other threads:[~2005-05-31 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 16:25 Problem Adding Transport Class support to fusion Moore, Eric Dean
2005-05-31 16:39 ` James Bottomley
2005-05-31 17:40 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31 21:38 Moore, Eric Dean
2005-05-30 21:55 James Bottomley

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=1117561255.4952.14.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Eric.Moore@lsil.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