From: James Bottomley <James.Bottomley@steeleye.com>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>, mjacob@feral.com
Subject: Feral Qlogic ISP driver up for testing
Date: 15 May 2003 11:58:41 -0500 [thread overview]
Message-ID: <1053017923.2267.76.camel@mulgrave> (raw)
I've taken Matthew Jacob's latest drop of the Feral ISP driver and put
it up under bitkeeper at
http://linux-scsi.bkbits.net/scsi-isp-2.5
I've plumbed it into the SCSI build and done some minor tweaking to make
it compile and run correctly in 2.5 (a missing vmalloc #include and the
irqreturn_t stuff).
If people could check it out, I'd be grateful.
I find on my 1280 board that it panics in isp_reset(), but that could
just be because I use exotic hardware (a PA-RISC C360 box) for testing.
James
next reply other threads:[~2003-05-15 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 16:58 James Bottomley [this message]
2003-05-15 17:03 ` Feral Qlogic ISP driver up for testing Christoph Hellwig
2003-05-15 17:13 ` James Bottomley
2003-05-15 17:25 ` Matthew Jacob
2003-05-15 17:30 ` James Bottomley
2003-05-15 17:32 ` Matthew Jacob
2003-05-15 17:23 ` Matthew Jacob
2003-05-15 18:05 ` Christoph Hellwig
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=1053017923.2267.76.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@digeo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mjacob@feral.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