public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
Date: Wed, 13 Dec 2006 01:09:02 +0100	[thread overview]
Message-ID: <20061213000902.GD28443@stusta.de> (raw)
In-Reply-To: <1165966274.5903.56.camel@mulgrave.il.steeleye.com>

On Tue, Dec 12, 2006 at 05:31:14PM -0600, James Bottomley wrote:
> On Tue, 2006-12-12 at 17:22 +0100, Adrian Bunk wrote:
> > The SCSI_SEAGATE driver has:
> > - already been marked as BROKEN in 2.6.0 three years ago and
> > - is still marked as BROKEN.
> > 
> > Drivers that had been marked as BROKEN for such a long time seem to be
> > unlikely to be revived in the forseeable future.
> > 
> > But if anyone wants to ever revive this driver, the code is still
> > present in the older kernel releases.
> 
> Would you care to explain the rationale for this, please.  If the driver
> had been riddled with errors and compilation problems, I might have
> acquiesced, but now I come to look it over, it seems structurally
> reasonably OK (we certainly have non-BROKEN worse ones) plus it compiles
> fine.  So I'm wondering why it's marked broken in the first place.
> 
> Since it was your original patch:
> 
> Author: Adrian Bunk <bunk@fs.tum.de>
> Date:   Mon Sep 1 19:22:52 2003 -0700
> 
>     [PATCH] Mark more drivers BROKEN{,ON_SMP}
>     
>     - let more drivers that don't compile depend on BROKEN
>     - MTD_BLKMTD is fixed, remove the dependency on BROKEN
>     - let all drivers that don't compile on SMP (due to cli/sti usage)
>       depend on a BROKEN_ON_SMP that is only defined if !SMP || BROKEN
>     - #include interrupt.h for dummy cli/sti/... in two files to fix the
>       UP compilation of these files
>     
>     I marked only drivers that are broken for a long time and where I don't
>     know about existing fixes with BROKEN or BROKEN_ON_SMP.
> 
> I'd like to know why it was marked BROKEN in the first place.


There must have been a compile error that has since been fixed, but I 
don't remember the details of this specific driver and I don't have 
such old compile logs anymore.


> Thanks,
> 
> James

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

  reply	other threads:[~2006-12-13  0:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 16:22 [2.6 patch] remove the broken SCSI_SEAGATE driver Adrian Bunk
2006-12-12 23:31 ` James Bottomley
2006-12-13  0:09   ` Adrian Bunk [this message]
2006-12-15 13:34     ` Krzysztof Halasa
2006-12-15 14:05       ` Oliver Neukum
2006-12-15 16:00       ` James Bottomley
2006-12-17 20:03         ` Krzysztof Halasa
2006-12-17 20:22           ` James Bottomley
2006-12-17 21:18             ` Krzysztof Halasa
2006-12-18  8:47               ` Arjan van de Ven
2006-12-18 13:48                 ` Krzysztof Halasa
2006-12-18 15:20                   ` Arjan van de Ven

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=20061213000902.GD28443@stusta.de \
    --to=bunk@stusta.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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