public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Aic7x_x_x 6.3.4 && Aic79xx 2.0.5 Updates
Date: Sat, 27 Dec 2003 08:47:44 -0700	[thread overview]
Message-ID: <3327750000.1072540064@aslan.btc.adaptec.com> (raw)
In-Reply-To: <1072537914.5494.5.camel@dhcp23.swansea.linux.org.uk>

> On Sad, 2003-12-27 at 04:26, Justin T. Gibbs wrote:
>> I'm sorry you feel that way.  I suppose I will just have to continue
>> to point distributors and users of this driver to my own patch sets since
>> that seems to be the only viable alternative you've given me.
>
> Is that an official Adaptec statement, or should I ask Adaptec if they
> can assist in resolving this matter ?
 
That is my statement.  You can escalate this matter to whatever formum
you feel is most appropriate.
 
That said, Adaptec's typical stance on these matters is that if a change
is required to these drivers in order to make them work correctly
(i.e. something required by a major customer) that for some reason is not
embedded, that providing separate DUD/RPM/SRC distributions to
our customers is sufficient.  This change is no different.  The current
SCSI layer offers no other alternative to having fully functional watchdog
recovery.  This is not a new revelation and my drivers are not the first
to take *extreme measures* to try and avoid the brokenness.  The changes
were not made in an attempt to be inflammatory, they were made to fix
real field issues that could be resolved within the driver in no other way.
 
James seems to imply that it is my responsibility as a "good open source
developer" to "contribute" the fixes to the SCSI layer to correct these
issues.  I would think that the SCSI layer maintainer would not only
understand these issues, but take up the charge of discussing and correcting
them.  Since we don't agree, on a fundamental level, on what the problem is
much less how to fix it, I think that having me go off and come up with fixes
would be counter productive to all involved.
 
If there is sincere interest in correcting error recovery in the Linux
SCSI layer, I'm still more than happy to give input and perhaps even
provide code.  But to say that I cannot embed a driver that has to skirt
mid-layer brokenness in order to be fully functional - regardless of how
it does that - until that brokenness can be corrected, is a disservice to
all users of this hardware.
 
--
Justin


  reply	other threads:[~2003-12-27 15:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 23:51 (unknown) Justin T. Gibbs
2003-06-03 23:58 ` Marc-Christian Petersen
2003-06-04  1:34 ` Aic7x_x_x 6.2.36 && Aic79xx 1.3.10 Updates Justin T. Gibbs
2003-12-24 16:58   ` Aic7x_x_x 6.3.4 && Aic79xx 2.0.5 Updates Justin T. Gibbs
2003-12-24 17:50     ` James Bottomley
     [not found]       ` <2148850000.1072292121@aslan.scsiguy.com>
2003-12-24 19:05         ` James Bottomley
2003-12-25  4:31           ` Justin T. Gibbs
2003-12-26 18:36             ` James Bottomley
2003-12-27  0:13               ` Justin T. Gibbs
2003-12-27  3:20                 ` James Bottomley
2003-12-27  4:26                   ` Justin T. Gibbs
2003-12-27  6:08                     ` Jeff Garzik
2003-12-27 15:11                     ` Alan Cox
2003-12-27 15:47                       ` Justin T. Gibbs [this message]
2003-12-27 15:52                     ` James Bottomley
2003-12-27 15:17               ` Alan Cox
2003-12-27 15:54                 ` James Bottomley
2003-12-27 23:55                   ` Alan Cox
2003-12-27 16:02                 ` Justin T. Gibbs

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=3327750000.1072540064@aslan.btc.adaptec.com \
    --to=gibbs@scsiguy.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.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