public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: patmans@us.ibm.com, mbligh@aracnet.com,
	James.Bottomley@steeleye.com, mikeand@us.ibm.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Broken SCSI code in the BK tree (was: 2.5.59-mm8)
Date: Thu, 6 Feb 2003 23:24:40 -0500	[thread overview]
Message-ID: <20030206232440.F19868@redhat.com> (raw)
In-Reply-To: <20030206201939.27216fb1.akpm@digeo.com>; from akpm@digeo.com on Thu, Feb 06, 2003 at 08:19:39PM -0800

On Thu, Feb 06, 2003 at 08:19:39PM -0800, Andrew Morton wrote:
> Doug Ledford <dledford@redhat.com> wrote:
> >
> > I would much prefer that people simply test out Matthew's
> > driver and use it instead.
> 
> Where is it?
> 
> http://www.feral.com/isp.html seems to be 2.4.x-only.

As answered elsewhere, the 2.5 port isn't done yet.  That's why I said in 
my email "if it's ready for 2.5" because I was afraid Matthew hadn't 
gotten around to doing the 2.5 update yet.  However, if no one else can do 
it, I can make a 2.5 update of this driver happen (I don't suspect it 
would be that hard actually, not *that* much has to change).

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  reply	other threads:[~2003-02-07  4:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  7:31 2.5.59-mm8 Andrew Morton
2003-02-04  8:02 ` 2.5.59-mm8 Joshua Kwan
2003-02-04  8:05   ` 2.5.59-mm8 Andrew Morton
2003-02-04  8:08     ` 2.5.59-mm8 Joshua Kwan
2003-02-04  8:09 ` 2.5.59-mm8 Martin J. Bligh
2003-02-04  8:17   ` 2.5.59-mm8 Andrew Morton
2003-02-04 22:15     ` Broken SCSI code in the BK tree (was: 2.5.59-mm8) Martin J. Bligh
2003-02-06  5:13       ` Martin J. Bligh
2003-02-06 20:50         ` Martin J. Bligh
2003-02-06 22:30           ` Martin J. Bligh
2003-02-06 23:25             ` James Bottomley
2003-02-07  1:24               ` Patrick Mansfield
2003-02-07  2:01                 ` Martin J. Bligh
2003-02-07  2:25                   ` Patrick Mansfield
2003-02-07  4:05                     ` Doug Ledford
2003-02-07  4:19                       ` Anton Blanchard
2003-02-07  8:50                         ` Mike Anderson
2003-02-07  4:19                       ` Andrew Morton
2003-02-07  4:24                         ` Doug Ledford [this message]
2003-02-07  4:35                           ` William Lee Irwin III
2003-02-07  4:53                             ` Matthew Jacob
2003-02-07  4:50                         ` Matthew Jacob
2003-02-07  4:28                       ` Martin J. Bligh
2003-02-04  9:07   ` 2.5.59-mm8 Dave Hansen
2003-02-04  9:18 ` 2.5.59-mm8 compile error in tcp_ipv6.c Helge Hafting
2003-02-04  9:21   ` Andrew Morton
2003-02-04  9:29     ` David S. Miller
2003-02-04  9:33 ` 2.5.59-mm8 Arjan van de Ven
2003-02-05  8:08 ` 2.5.59-mm8 Mike Galbraith

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=20030206232440.F19868@redhat.com \
    --to=dledford@redhat.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mikeand@us.ibm.com \
    --cc=patmans@us.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