public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Jacob <mjacob@feral.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: Feral Qlogic ISP driver up for testing
Date: Thu, 15 May 2003 10:32:48 -0700 (PDT)	[thread overview]
Message-ID: <20030515103127.K12807@wonky.in0.lcl> (raw)
In-Reply-To: <1053019841.2267.85.camel@mulgrave>


Oh- okay. The 2.5 tree I had that was different isn't all *that*
different. But I was taken a bit by surprise again. By all means- test
away as much as you like and send bug reports.

I'm sure that there are boatloads of issues. For example, I just fixed a
bug yesterday that had threads getting left around after module unload
for 2.4.


On Thu, 15 May 2003, James Bottomley wrote:

> On Thu, 2003-05-15 at 12:25, Matthew Jacob wrote:
> >
> >
> > The tarball doesn't get updated as frequently as my BK tree, and the BK
> > tree for 2.5 is different...
> >
> > bk://bitkeeper.feral.com:9002
>
> Hmm, well, the bitkeeper tree is where I got the files from.
>
> We can certainly hold off on integrating it (that's why I put it into a
> separate BK tree).  However, unless there are any really nasty lurking
> bugs, I'd like to get those people who can at least to test it.
>
> James
>
>
>

  reply	other threads:[~2003-05-15 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 16:58 Feral Qlogic ISP driver up for testing James Bottomley
2003-05-15 17:03 ` 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 [this message]
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=20030515103127.K12807@wonky.in0.lcl \
    --to=mjacob@feral.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@digeo.com \
    --cc=hch@infradead.org \
    --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