From: Patrick Mansfield <patmans@us.ibm.com>
To: Andries.Brouwer@cwi.nl
Cc: zwane@holomorphy.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
mdharm-kernel@one-eyed-alien.net
Subject: Re: inquiry in scsi_scan.c
Date: Mon, 6 Jan 2003 12:52:43 -0800 [thread overview]
Message-ID: <20030106125243.A9710@beaverton.ibm.com> (raw)
In-Reply-To: <UTC200301052142.h05LgkH25404.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Sun, Jan 05, 2003 at 10:42:46PM +0100
On Sun, Jan 05, 2003 at 10:42:46PM +0100, Andries.Brouwer@cwi.nl wrote:
> Zwane Mwaikambo writes:
>
> > This looks related to something i also bumped into
> >
> > scsi scan: host 2 channel 0 id 0 lun 0 identifier too long
>
> Sounds familiar. Please try the below (on 2.5.54).
>
> Andries
>
Instead of truncating the id, we need a new scsi_uid field allocated
to whatever size required. And, a descriptive string put in the name,
rather than the id, such as:
scsi disk
scsi processor
scsi tape
Even if the id is truncated, that information has to be available.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-01-06 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 21:42 inquiry in scsi_scan.c Andries.Brouwer
2003-01-06 20:52 ` Patrick Mansfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 21:35 Andries.Brouwer
2003-01-05 22:05 ` Luben Tuikov
2003-01-05 13:07 Andries.Brouwer
2003-01-05 19:36 ` Luben Tuikov
2003-01-05 20:54 ` Zwane Mwaikambo
2003-01-05 20:54 ` Zwane Mwaikambo
2003-01-04 3:24 Andries.Brouwer
2003-01-04 3:07 Andries.Brouwer
2003-01-05 0:41 ` Matthew Dharm
2003-01-04 0:21 Andries.Brouwer
2003-01-04 1:04 ` Matthew Dharm
2003-01-04 2:14 ` Douglas Gilbert
2003-01-04 2:44 ` Patrick Mansfield
2003-01-05 0:45 ` Matthew Dharm
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=20030106125243.A9710@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=zwane@holomorphy.com \
/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.