Is there any news on that? Can we use the scsi_get/put_command() functions for allocating a "struct scsi_cmnd" or should we allocate it with kmalloc() or somehow like that? Or, Christoph, did you already make the second patch for the gdth driver?
We want to bring the gdth driver up to date as soon as possible. Any help is greatly appreciated!
Thanks,
Achim
=======================
Achim Leubner
Software Engineer / RAID drivers
ICP vortex GmbH / Adaptec Inc.
Phone: +49-351-8718291
-----Original Message-----
From: Leubner, Achim
Sent: Dienstag, 18. April 2006 16:41
To: 'Christoph Hellwig'; [email protected]; [email protected]
Subject: RE: HEADS UP for gdth driver users
Hi all,
The patch looks good for 2.6.17-rc1. Christoph, did you already make the second patch for the real switchover?
Will only the scsi_allocate_request()/scsi_do_req()/scsi_release_request() be removed in the next kernel releases? - I'm wondering if I could use the scsi_get_command()/scsi_put_command() functions to get a Scsi_Cmnd struct. and to send it to the gdth_queuecommand()/gdth_next(). I'm willing to make and test the second patch but please give me some hints what functions you plan to kill and what function we can still use.
Thanks & Regards,
Achim
=======================
Achim Leubner
Software Engineer / RAID drivers
ICP vortex GmbH / Adaptec Inc.
Phone: +49-351-8718291
-----Original Message-----
From: Christoph Hellwig [mailto:[email protected]]
Sent: Mittwoch, 8. März 2006 14:20
To: [email protected]; [email protected]; Leubner, Achim
Subject: HEADS UP for gdth driver users
Hi folks,
the gdth driver is the only driver using (and in this case abusing) the
scsi_request interface we plan to kill for 2.6.17. I've sent a patch
that's a first step to convert the driver away from it a few weeks ago
but didn't get any response. I urgently need testers to keep the driver
for 2.6.17+. Else it'll be marked broken until we get a person to help
testing the changes needed to resurrect it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
