All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Requested changes for the SCSI error handler
Date: Tue, 8 Jun 2004 11:39:06 -0700	[thread overview]
Message-ID: <20040608183905.GA1360@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0406081430220.649-100000@ida.rowland.org>

Alan Stern [stern@rowland.harvard.edu] wrote:
> On 8 Jun 2004, James Bottomley wrote:
> 
> > Well, how about a compromise?  I like the ability to alter the host
> > settle time; however, I think turning these over to the driver to sort
> > out how it pleases gives the LLD more control in this situation,
> > certainly for the HOST reset.
> > 
> > I'm less sure that a bus reset timeout belongs in the LLD, but I suppose
> > that could be pulled into the SPI transport class eventually.
> > 
> > So, what about Alan's approach using a single flag to give the LLD
> > control, but give it control for both the host and bus resets?
> 
> Sorry to appear slow... but isn't that exactly what my patch did?

Yes. That is what I thought you sent. 

-andmike
--
Michael Anderson
andmike@us.ibm.com


  reply	other threads:[~2004-06-08 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 18:50 Requested changes for the SCSI error handler Alan Stern
2004-06-01 19:58 ` James Bottomley
2004-06-01 20:29   ` Alan Stern
2004-06-01 20:46     ` James Bottomley
2004-06-04 20:59       ` Alan Stern
2004-06-04 23:23         ` Mike Anderson
2004-06-05 22:41           ` Alan Stern
2004-06-08 16:26           ` James Bottomley
2004-06-08 17:19             ` Mike Anderson
2004-06-08 18:31             ` Alan Stern
2004-06-08 18:39               ` Mike Anderson [this message]
2004-06-08 22:00               ` 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=20040608183905.GA1360@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.