From: Mike Anderson <andmike@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_debug 1.64 , remove detect(), "hotplug" hosts
Date: Sat, 9 Nov 2002 17:27:48 -0800 [thread overview]
Message-ID: <20021110012748.GA1301@beaverton.ibm.com> (raw)
In-Reply-To: <3DCCE2E6.6050800@torque.net>
Douglas Gilbert [dougg@torque.net] wrote:
> Notes:
> - Christoph and Mike A. are pulling me in 2 different
> directions. In this case Christoph got to me first
> so I have moved along that direction. Mike's
> "/sysfs/bus/scsi_dbg_fake" has me perplexed ...
I was not trying to pull in another direction, but my patches may have
had to many steps in one chunk that may have made it look that way.
I have split the functionality of my previous patch for scsi_debug into
smaller chunks. I believe there are advantages to scsi mid code and the
device model code in making scsi_debug look more like a real adapter.
I need to do more testing hopefully I can send you something Sunday if
you are interested.
> - rmmod and subsequent modprobe's on scsi_debug
> sometimes blow up.
> Hopefully Patrick's fix (not in bk3?) addresses that.
I would use the changes that Patrick sent out as we had problems
with insmod / rmmod without these. I previously sent these to Mochel,
but he was in the process of moving and they probably will not show up
in a bk ( or fixes like these) until he can respond.
It seemed when I was re-working my patches that num_hosts_present is
used during scsi_debug_exit to cleanup, but is not incremented during
sdebug_add_host_write. There seems to a mixed use of scsi_debug_add_host
and num_hosts_present.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2002-11-10 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 10:26 [PATCH] scsi_debug 1.64 , remove detect(), "hotplug" hosts Douglas Gilbert
2002-11-10 1:27 ` Mike Anderson [this message]
2002-11-11 1:44 ` 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=20021110012748.GA1301@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--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 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.