From: Christoph Hellwig <hch@lst.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Christoph Hellwig <hch@lst.de>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] clean up some more tmscsim scan logic
Date: Tue, 24 Aug 2004 13:36:41 +0200 [thread overview]
Message-ID: <20040824113641.GB16546@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0408192300530.5248@poirot.grange>
On Thu, Aug 19, 2004 at 11:16:00PM +0200, Guennadi Liakhovetski wrote:
> That's actually what I was reading and that's where I didn't understand:
>
> * Notes:
> * This has the unfortunate side effect that if a shost adapter does
> * not automatically request sense information, that we end up shutting
> * it down before we request it. All shosts should be doing this
> ^^^^
> * anyways, so for now all I have to say is tough noogies if you end up
> * in here. On second thought, this is probably a good idea. We
> * *really* want to give authors an incentive to automatically request
> * this.
>
> So, I failed to understand if "this" above means "All shosts should be
> automatically requesting sense" or the opposite.
I'm pretty sure it means the HBA or LLDD should do it. I'll send James
a patch to fix up the wording.
> Then the "second
> thought"... So, you mean LLDs should really auto-request sense on
> failures. Well, if we detect an error condition when we are CONNECTED to a
> host, it should be possible to directly send a REQUEST SENSE - the bus
> should be ours at this time, right?
I think so.
next prev parent reply other threads:[~2004-08-24 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 16:33 [PATCH] clean up some more tmscsim scan logic Christoph Hellwig
2004-08-17 20:17 ` Guennadi Liakhovetski
2004-08-19 11:33 ` Christoph Hellwig
2004-08-19 21:16 ` Guennadi Liakhovetski
2004-08-19 22:07 ` Luben Tuikov
2004-08-20 20:36 ` Guennadi Liakhovetski
2004-08-21 22:00 ` Guennadi Liakhovetski
2004-08-24 11:36 ` Christoph Hellwig [this message]
2004-08-17 20:17 ` Guennadi Liakhovetski
2004-08-17 20:21 ` 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=20040824113641.GB16546@lst.de \
--to=hch@lst.de \
--cc=g.liakhovetski@gmx.de \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).