From: Willem Riede <wrlk@riede.org>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org
Subject: Re: buggy scsi_register behaviour in 2.5.51
Date: Fri, 20 Dec 2002 09:46:48 -0500 [thread overview]
Message-ID: <20021220144648.GW7990@linnie.riede.org> (raw)
In-Reply-To: <3E006692.7020503@torque.net>; from dougg@torque.net on Wed, Dec 18, 2002 at 07:14:10 -0500
On 2002.12.18 07:14 Douglas Gilbert wrote:
>
> These are documented in Documentation/scsi/scsi_mid_low_api.txt .
> If you find mistakes or the explanation is not clear then
> complain to me.
Your doc doesn't define the second parameter to scsi_add_host.
Can you explain what the purpose is of the struct device *dev
and how I'm supposed to pull one out of my hat in __init?
I notice that the old style registration doesn't bother with
shost->host_gendev.
Thanks, Willem Riede.
next prev parent reply other threads:[~2002-12-20 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 3:27 buggy scsi_register behaviour in 2.5.51 Douglas Gilbert
2002-12-17 11:47 ` Willem Riede
2002-12-18 12:14 ` Douglas Gilbert
2002-12-18 23:20 ` Willem Riede
2002-12-20 14:46 ` Willem Riede [this message]
2002-12-18 1:52 ` Willem Riede
-- strict thread matches above, loose matches on Subject: below --
2002-12-17 0:50 Willem Riede
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=20021220144648.GW7990@linnie.riede.org \
--to=wrlk@riede.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