From: Dave C Boutcher <sleddog@us.ibm.com>
To: Jan-Frode Myklebust <mykleb@no.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ibmvscsi: handle re-enable firmware message
Date: Thu, 19 Jan 2006 14:55:30 -0600 [thread overview]
Message-ID: <20060119205530.GB21420@cs.umn.edu> (raw)
In-Reply-To: <slrndsvtrd.od7.mykleb@99RXZYP.ibm.com>
On Thu, Jan 19, 2006 at 09:32:45PM +0100, Jan-Frode Myklebust wrote:
> Is there also an updated ibmvscsi-server patch somewhere?
No, I gave up on pushing that driver in its current form towards
mainline, and I've been tied up for the last month or so on another
project. The long term answer is to tie into the work Mike Christie &
Co. are doing....
I have somewhat reliable reports that the previous patches still work on
2.6.15. We also have a sourcforge project with the ibmvscsis driver.
If you are using it heavily, let me know and I'll put a little more
effort into keeping it current until an alternative is available.
--
Dave Boutcher
prev parent reply other threads:[~2006-01-19 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 19:34 [PATCH] ibmvscsi: handle re-enable firmware message Dave C Boutcher
2006-01-19 20:32 ` Jan-Frode Myklebust
2006-01-19 20:55 ` Dave C Boutcher [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=20060119205530.GB21420@cs.umn.edu \
--to=sleddog@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mykleb@no.ibm.com \
/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