public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Finn Thain <fthain@telegraphics.com.au>,
	linux-m68k@vger.kernel.org, linux-scsi@vger.kernel.org,
	Sam Creasey <sammy@sammy.net>,
	Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: mac scsi, ncr5380
Date: Tue, 30 Sep 2008 04:45:37 -0400	[thread overview]
Message-ID: <20080930084536.GA28524@infradead.org> (raw)
In-Reply-To: <48DF8398.30000@panasas.com>

On Sun, Sep 28, 2008 at 04:16:08PM +0300, Boaz Harrosh wrote:
> >From a SCSI generic point of view. The current xxx_NCR5380 remind me allot
> of the old ESP drivers stack. At-least at the surface level of the patches
> I sent for both these drivers. I was lucky, at the end, to only send the
> xxx_NCR5380 patches, because, as strongly recommended by Christoph Hellwig
> (CCed), the old ESP stack was brilliantly replaced by a new one. That is 1/10
> the size of the old one, and currently supports most of the interesting devices
> out there. My unsent patches was a catalyst, for the now broken old-driver-stack,
> to be removed quickly. And it seems every one is happy.
> 
> My point being, If you are looking to do a major cleanup work, on all these
> 1/2 forks. Maybe give a hard thought on just trashing the all thing and crafting
> a completely new stack, 1/10 the size and much simpler, modern, and maintainable.

That would we very nice.  All 5380 drivers are in a really sorry state,
and a new one even if only working for sun3 and atari for now would be a
great change.  I'm not even sure if we have any users left for the PC
and arm 5380 drivers.


  reply	other threads:[~2008-09-30  8:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26  8:27 mac scsi, ncr5380 Finn Thain
2008-09-26 14:40 ` [linux-m68k] " Sam Creasey
2008-09-27  3:10 ` Michael Schmitz
2008-09-27  8:00   ` Finn Thain
2008-09-27 19:12     ` Brad Boyer
2008-09-28 11:28       ` Finn Thain
2008-09-28 18:03         ` Brad Boyer
2008-09-29 13:22           ` Finn Thain
2008-09-29 23:18             ` Brad Boyer
2008-09-30  8:40               ` Finn Thain
2008-09-29 21:03         ` Riccardo
2008-09-30  6:18           ` Finn Thain
2008-09-28 13:16 ` Boaz Harrosh
2008-09-30  8:45   ` Christoph Hellwig [this message]
2008-10-01  8:04     ` Finn Thain
2008-10-01  7:19   ` Finn Thain
2008-10-02  8:33     ` Boaz Harrosh

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=20080930084536.GA28524@infradead.org \
    --to=hch@infradead.org \
    --cc=bharrosh@panasas.com \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sammy@sammy.net \
    --cc=schmitz@biophys.uni-duesseldorf.de \
    /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