Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Miller <davem@davemloft.net>
Cc: linux-m68k@vger.kernel.org,
	James.Bottomley@HansenPartnership.com, bharrosh@panasas.com,
	hch@infradead.org, macro@linux-mips.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] Remove of old NCR53C9x/esp family of drivers
Date: Fri, 4 Jan 2008 10:59:35 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801041054130.27528@anakin> (raw)
In-Reply-To: <20080103.150204.101269827.davem@davemloft.net>

On Thu, 3 Jan 2008, David Miller wrote:
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> > On Thu, 3 Jan 2008, James Bottomley wrote:
> > > On Thu, 2008-01-03 at 17:40 +0200, Boaz Harrosh wrote:
> > > > As recommended by Christoph Hellwig. There is no use
> > > >  of Fixing these drivers, since there is a much simpler
> > > >  and modern esp infrastructure with David Miller's esp_scsi
> > > > 
> > > >   - Remove all driver files dependent on NCR53C9x.c
> > > >         deleted:    drivers/scsi/NCR53C9x.c
> > > >         deleted:    drivers/scsi/NCR53C9x.h
> > > >         deleted:    drivers/scsi/blz1230.c
> > > >         deleted:    drivers/scsi/blz2060.c
> > > >         deleted:    drivers/scsi/cyberstorm.c
> > > >         deleted:    drivers/scsi/cyberstormII.c
> > > >         deleted:    drivers/scsi/dec_esp.c
> > > >         deleted:    drivers/scsi/fastlane.c
> > > >         deleted:    drivers/scsi/mac_esp.c
> > > >         deleted:    drivers/scsi/mca_53c9x.c
> > > >         deleted:    drivers/scsi/oktagon_esp.c
> > > >         deleted:    drivers/scsi/oktagon_io.S
> > > >         deleted:    drivers/scsi/sun3x_esp.c
> > > > 
> > > >   - Remove above list from drivers/scsi/Kconfig &&
> > > > drivers/scsi/Makefile
> > > 
> > > OK, I'll split this into four pieces for scsi-pending, since there are
> > > three separate interest groups with signoffs to collect (MCA, m68k and
> > > alpha) plus the core removal.
> > 
> > Anybody who can look into converting the m68k NCR53C9x drivers and has
> > hardware to test (some of) them? I don't think we can afford losing one
> > third of our SCSI drivers...
> 
> We can't wait forever, and effort spent maintaining the old
> rotting drivers is effort that should instead be spent on
> the converted new drivers.
> 
> Instead of seeing conversions being written, we've been hearing this
> swan song from the m68k crowd forever, it's getting quite old.

quite old == the new esp_scsi arrived in April 2007. On the m68k timescale,
this is just a split-second ago. Following this logic, it's a surprise
OSS hasn't been removed completely ;-)

> I totally object to keeping these things around any longer.  And this
> I support these changes going in.

BTW, I hope you do remember why NCR53C9x.[ch] incarnated in the first place...

OK, we'll see what we can do...

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-01-04 10:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 15:17 [PATCH 0/1] Remove of old NCR53C9x/esp family of drivers Boaz Harrosh
2008-01-03 15:40 ` [PATCH 1/1] " Boaz Harrosh
2008-01-03 18:16   ` James Bottomley
2008-01-03 19:05     ` Geert Uytterhoeven
2008-01-03 19:19       ` James Bottomley
2008-01-03 19:46         ` Michael Schmitz
2008-01-03 23:02       ` David Miller
2008-01-04  9:59         ` Geert Uytterhoeven [this message]
2008-01-04 11:05           ` Finn Thain
2008-01-04 11:49             ` David Miller
2008-01-05  5:07               ` Finn Thain
2008-02-21  7:59                 ` mac_esp and PIO, was " Finn Thain
2008-01-07  6:07       ` Kars de Jong
2008-01-31 18:08         ` James Bottomley
2008-01-31 18:55           ` Geert Uytterhoeven
2008-01-31 19:06             ` Boaz Harrosh
2008-01-31 19:31             ` James Bottomley
2008-02-08  6:04               ` 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=Pine.LNX.4.64.0801041054130.27528@anakin \
    --to=geert@linux-m68k.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bharrosh@panasas.com \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=macro@linux-mips.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