public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_mid_low_api.txt for 2.5.46-bk3
Date: Fri, 8 Nov 2002 02:46:23 +0000	[thread overview]
Message-ID: <20021108024623.A19182@infradead.org> (raw)
In-Reply-To: <3DCB0E51.5070407@torque.net>; from dougg@torque.net on Fri, Nov 08, 2002 at 12:07:29PM +1100

On Fri, Nov 08, 2002 at 12:07:29PM +1100, Douglas Gilbert wrote:
> This patch against 2.5.46-bk3 is work in progress
> (since the interface is in flux). It dusts of some
> cobwebs, removes politically incorrect typedefs and

I'd suggest to leave them in where the struct names are raraly used and even
worse (e.g. struct SHT), I'm probably going to a do a big cleansweap to
give them saner struct names soon, and the fewer users they acquired until
then the better..

> describes slave_attach() and slave_detach(). It
> removes the revoke() description (per hch? changes).

Patrick did it.

> Is a section describing mid level functions provided
> for LLDDs (e.g. scsi_adjust_queue_depth() )
> warranted?

LLDD = Low Level Driver Developer?

It looks like a good idea to me, but I wonder whether that should be
a separate Document.  BTW, what about movinf this and the other docs
(e.g. README.*) in drivers/scsi/ to Documentation/scsi/ ?

Another things that's worth mentioning is that ->detect and ->release are
option now if you don't write a scsi_module.c-style driver.

And thanks a lot for caring for the scsi documentation, I usually try to update
it for my changes, but you do a much better job..

  reply	other threads:[~2002-11-08  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08  1:07 [PATCH] scsi_mid_low_api.txt for 2.5.46-bk3 Douglas Gilbert
2002-11-08  2:46 ` Christoph Hellwig [this message]
2002-11-08  3:13 ` Randy.Dunlap
2002-11-08  5:01   ` Doug Ledford

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=20021108024623.A19182@infradead.org \
    --to=hch@infradead.org \
    --cc=dougg@torque.net \
    --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