From: Douglas Gilbert <dougg@torque.net>
To: Christoph Hellwig <hch@lst.de>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] give ->proc_info a struct Scsi_Host * parameter
Date: Tue, 13 May 2003 17:00:54 +1000 [thread overview]
Message-ID: <3EC09826.20406@torque.net> (raw)
In-Reply-To: <20030512160344.A11185@lst.de>
Christoph Hellwig wrote:
> Yeah, I know the method is obsolete but for proper refcounting we
> need to get rid of all those scsi_host_hn_get() abusers.
>
> scsi_host_hn_get() and scsi_host_put() are not exported anymore
> after this patch.
Christoph,
I'm working on a patch to add a virtual device node in the
sg driver tentatively called /dev/sgbind. It follows on
from a suggestion by Patrick Mansfield recently to allow
device scanning from the user space.
It is work in progress and I will send some patches
and/or RFCs shortly. To do this I need access to
scsi_host_hn_get() and scsi_host_put() so please leave
them exported.
Doug Gilbert
next prev parent reply other threads:[~2003-05-13 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 14:03 [PATCH] give ->proc_info a struct Scsi_Host * parameter Christoph Hellwig
2003-05-13 7:00 ` Douglas Gilbert [this message]
2003-05-13 6:59 ` 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=3EC09826.20406@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@steeleye.com \
--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