From: Greg KH <greg@kroah.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org, Kai.Makisara@kolumbus.fi, wrlk@riede.org
Subject: Re: [PATCH] sg driver against lk 2.6.1-bk6
Date: Wed, 21 Jan 2004 09:16:17 -0800 [thread overview]
Message-ID: <20040121171617.GB12384@kroah.com> (raw)
In-Reply-To: <400E706A.1050008@torque.net>
On Wed, Jan 21, 2004 at 10:28:26PM +1000, Douglas Gilbert wrote:
> This patch is against the sg driver found in lk 2.6.1-bk6 .
> It is an update on the sg patch sent in the "devices with more
> than one node" thread:
> http://marc.theaimsgroup.com/?l=linux-scsi&m=107415435300783&w=2
>
> The "simple_class" interface in the mm tree has mutated to
> "class_simple" en route to 2.6.1-bk6. There is now an opaque
> struct class_simple ** which does not seem to allow sg to put
> its driver parameters under the /sys/class/scsi_generic
> directory [which is not relevant to st and osst].
>
> $ cd /sys/class/scsi_generic/
> $ tree
> .
> `-- sg0
> |-- dev
> `-- device -> ../../../devices/pseudo_0/adapter0/host0/0:0:0:0
>
> $ cd sg0/device/
> $ tree
> .
> |-- delete
> |-- detach_state
> |-- device_blocked
> |-- generic -> ../../../../../class/scsi_generic/sg0
> |-- model
> |-- online
> |-- power
> | `-- state
> |-- queue_depth
> |-- rescan
> |-- rev
> |-- scsi_level
> |-- type
> `-- vendor
Nice, looks good.
> ** struct class_simple's definition is "hidden" in
> /drivers/base/class_simple.c
Is this a problem? I figured that if you want access to a struct class,
then you need to go through the "hassle" of dealing with class devices
and classes on your own. It's a trade off. Do you find this too
limiting for you?
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-21 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 12:28 [PATCH] sg driver against lk 2.6.1-bk6 Douglas Gilbert
2004-01-21 17:16 ` Greg KH [this message]
2004-01-26 12:01 ` Douglas Gilbert
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=20040121171617.GB12384@kroah.com \
--to=greg@kroah.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=wrlk@riede.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.