All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: alan@lxorguk.ukuu.org.uk, 76306.1226@compuserve.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges
Date: Thu, 10 Apr 2003 13:20:55 +0200	[thread overview]
Message-ID: <20030410132055.1745749c.skraw@ithnet.com> (raw)
In-Reply-To: <194120000.1049909641@aslan.btc.adaptec.com>

On Wed, 09 Apr 2003 11:34:01 -0600
"Justin T. Gibbs" <gibbs@scsiguy.com> wrote:

> > On Mer, 2003-04-09 at 02:21, Chuck Ebbert wrote:
> >> And your code goes for long periods of time without merging good fixes,
> >> like this one (from 2.4.20):
> > 
> > Which is one reason Justin's patches don't get merged. They are giant
> > changes which back out other clear corrections.
> 
> This tells me two things:
> 
> 1) You don't trust maintainers.  If a maintainer can't make large changes,
>    who can?
> 
> 2) When a maintainer makes a mistake (fails to integrate a good change,
>    or introduces a bug), the maintainers changes are simply dropped rather
>    then notify (either politely or not I don't much care) the maintainer
>    of his/her mistake.
> 
> Neither of the above applied to integration of the aic79xx driver into
> the 2.4.X tree, but it still took something like 8 months.
> 
> There must be a better way.

As I am probably one of the victims of these differing opinions, can anyone
tell me where to get a really-known-to-work aic-driver for 2.4? I am
experiencing zapping-black events while reading from a SDLT drive (writing to
it does fine).

Short hardware story:
02:03.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
02:03.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)

Host: scsi0 Channel: 00 Id: 08 Lun: 00
  Vendor: IBM      Model: IC35L073UWDY10-0 Rev: S21E
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 02 Lun: 00
  Vendor: QUANTUM  Model: SDLT320          Rev: 3838
  Type:   Sequential-Access                ANSI SCSI revision: 02

Any hints welcome

Regards,
Stephan


  reply	other threads:[~2003-04-10 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  1:21 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Chuck Ebbert
2003-04-09  2:13 ` Justin T. Gibbs
2003-04-09 11:13 ` Alan Cox
2003-04-09 17:34   ` Justin T. Gibbs
2003-04-10 11:20     ` Stephan von Krawczynski [this message]
2003-04-10 16:44       ` [PATCH] aic7* claims all checked EISA io ranges Justin T. Gibbs
2003-04-11  8:51         ` Stephan von Krawczynski
2003-04-11 11:39         ` Stephan von Krawczynski
  -- strict thread matches above, loose matches on Subject: below --
2003-04-08 23:07 James Bottomley
2003-04-08 23:12 ` Justin T. Gibbs
2003-04-08 23:28   ` James Bottomley

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=20030410132055.1745749c.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=76306.1226@compuserve.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.