From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Douglas Gilbert <dougg@torque.net>,
James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] switch scsi upper driver probing to the driver model
Date: Mon, 19 May 2003 12:02:27 -0700 [thread overview]
Message-ID: <20030519190227.GA25948@kroah.com> (raw)
In-Reply-To: <20030517091352.A13403@lst.de>
On Sat, May 17, 2003 at 09:13:52AM +0200, Christoph Hellwig wrote:
> On Sat, May 17, 2003 at 01:59:52PM +1000, Douglas Gilbert wrote:
> > It was my understanding that the device model has been
> > recently modified by Greg KH to cope with the dual nature
> > of the interface that sg causes. Evidently similar situations
> > occur elsewhere in the kernel.
>
> Greg, any comments on this? I haven't found any code like that
> in drivers/base/ and I can't understand how this is supposed to work..`
I don't really know what you all are talking about here, but...
In talking with Mike Anderson about the driver class code changes, he
and I agreed that sg could just be made a struct class_device. It could
go under a "scsi" class if you want, and would point to the scsi devices
(in the device tree) that the sg driver is bound to.
Does that make more sense?
thanks,
greg k-h
next prev parent reply other threads:[~2003-05-19 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 16:20 [PATCH] switch scsi upper driver probing to the driver model Christoph Hellwig
2003-05-16 23:57 ` Mike Anderson
2003-05-17 2:25 ` Willem Riede
2003-05-17 7:16 ` Christoph Hellwig
2003-05-17 9:17 ` Christoph Hellwig
2003-05-17 16:35 ` Mike Anderson
2003-05-17 9:59 ` Kai Makisara
2003-05-17 15:08 ` Christoph Hellwig
2003-05-17 16:19 ` James Bottomley
2003-05-18 9:35 ` Kai Makisara
2003-05-17 3:59 ` Douglas Gilbert
2003-05-17 7:13 ` Christoph Hellwig
2003-05-19 19:02 ` Greg KH [this message]
2003-05-17 8:32 ` Jens Axboe
2003-05-17 12:52 ` Willem Riede
2003-05-19 21:38 ` Patrick Mansfield
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=20030519190227.GA25948@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=hch@lst.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