[7520] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: SCSI sub-system changes

daemon@ATHENA.MIT.EDU (Alexander Viro)
Fri Nov 12 12:09:15 1999

Date:   Fri, 12 Nov 1999 11:55:33 -0500 (EST)
From: Alexander Viro <viro@math.psu.edu>
To: Douglas Gilbert <dgilbert@724.com>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <BF2A97E56F4BD311AB0A009027858CDF1AA359@mail.724.com>
Message-ID: <Pine.GSO.4.10.9911121141490.15376-100000@weyl.math.psu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Fri, 12 Nov 1999, Douglas Gilbert wrote:

> Alexander,
> Did you think of posting an alert to the linux-scsi list about the
> changes to the mid-level and most of the low level drivers?

My fault. Changes were in interaction with procfs. Which was _badly_ broken.
From the drivers' POV the only change being: forget about proc_dir_entry,
leave ->proc_dir initialized with NULL and set ->proc_name to the string
constant (name of subdirectory in /proc/scsi). All you need to care about
is that any pair of drivers that can happen on the same box must have
different ->proc_name. _Always_ had to. So Amiga ESP-based cards went from
/proc/scsi/esp to /proc/scsi/esp-<driver_name>.

Another change: SCSI_IOCTL_GET_IDLUN returns host_no in place of driver
type.

> I know of one very frustrated maintainer (who works for a HBA
> manufacturer) who has been wondering why his patches have
> now been ignored for the 4th time. Is there a patch "lock" on
> the SCSI sub-system in 2.3 ?

No idea. Ask Linus and Alan.
						Al
-- 
All that blue light from Orthanc at night? That was Saruman, trying to
moderate news.admin.palantir-abuse.sightings.
					Mike Andrews in the Monastery


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post