No, that's not true; we are TOTALLY committed to getting all of our drivers in the upstream kernel. I have been working on the ISCSI driver cleanup to the level of our Fibre Channel driver as Andrew has done. I'm making it conform to the current linux-scsi API, ISCSI transport, and stripping out all of the failover baggage. My goal is the have something upstream in 2 - 3 weeks, if not before. -----Original Message----- From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi-owner@xxxxxxxxxxxxxxx] On Behalf Of Christoph Hellwig Sent: Wednesday, April 20, 2005 1:49 AM To: open-iscsi@xxxxxxxxxxxxxxxx Cc: linux-iscsi development team; linux-scsi@xxxxxxxxxxxxxxx Subject: Re: 5.x branch mainline kernel push in two weeks? On Wed, Apr 20, 2005 at 01:29:11AM -0700, Mike Christie wrote: > Are you going to try and push someone like qla4010 which has a similar > interface to qla2xxx (it uses the msg box interface) to use the netlink > interface? With a lot of the iscsi stuff masked away it seems a little > difficult to go the extent open-iscsi did? I'm not sure we should care too much about the qla4xxx driver. It's never been posted to linux-scsi, and the driver they pushed to SuSE ignores everything we've said about scsi low-level drivers. It looks like the iSCSI part of Qlogic simply doesn't care about Linux (that is upstream, not the major forks) - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
