public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Itai Nahshon <nahshon@actcom.co.il>
To: Luben Tuikov <luben@splentec.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Fwd: Patch - SCSI host numbers - please apply
Date: Wed, 19 Jun 2002 03:03:45 +0300	[thread overview]
Message-ID: <200206190303.45188.nahshon@actcom.co.il> (raw)
In-Reply-To: <3D0FA398.8DA6C959@splentec.com>

On Wednesday 19 June 2002 00:18 am, Luben Tuikov wrote:
> Itai,
>
>
> After applying your patch to 2.4.18, I see the following
> problems:

Well, I just tried that with 2.4.18-pre10 + my patch and I do not
see any of the problems that you described. I suspect there
is something wrong with your configuration or with the
way that you run your tests.

I first loaded ide-scsi (which got host_no 0) and then
the object that I got from compiling yout code with
MaxHosts=30 (and it got host_nos 1 .. 30).
Removng the modules worked OK too. The hosts were
unregistered and off course, no oops.
Then reloaded scsi_reg.o with MaxHosts=100. Again no
problem.

My configuration:
RedHat 7.2, non-SMP. All the updates from RedHat applied +KDE-3.0.
Relevant RPMS:
	gcc-2.96-98
	cpp-2.96-98
	binutils-2.11.90.0.8-11
	modutils-2.4.13-0.7.1

The kernel source tree is symbolic linked to /usr/src/linux .
Your code extracted to /usr/src/scsi_reg/ .


-- Itai


  reply	other threads:[~2002-06-19  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200206171604.57115.nahshon@actcom.co.il>
     [not found] ` <3D0E4F4F.1D3D68B3@splentec.com>
     [not found]   ` <200206181514.52827.nahshon@actcom.co.il>
2002-06-18 21:18     ` Fwd: Patch - SCSI host numbers - please apply Luben Tuikov
2002-06-19  0:03       ` Itai Nahshon [this message]
2002-06-19 16:26         ` Luben Tuikov

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=200206190303.45188.nahshon@actcom.co.il \
    --to=nahshon@actcom.co.il \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luben@splentec.com \
    --cc=marcelo@conectiva.com.br \
    /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