Karen Xie wrote:
Hi, Dave & Mike,
I guess I need some clarification on how this driver code could be merged.
I think you want to send a patch with the entire driver like you were
before. Do not send against my branch so James and others do not have to
dig around in there.
The cxgb3i driver addition consists of 2 parts:
1. the new cxgb3i driver. It resides under drivers/scsi, this part has the dependency on the open-iscsi core changes I referred in the previous email. I was under the impression this goes into scsi-misc?
2. some iscsi related changes in cxgb3 driver (driver/net). This part does not have any dependency. Dave, I suppose this part goes into net-next? If so, this does not need Mike's patch at all.
There is no dependency with network stuff right (just the cxgb3 driver
which is upstream already)? If so I think it would be easier to just
send the driver through James.
Thanks a lot.
Karen
-----Original Message-----
From: David Miller [mailto:davem@xxxxxxxxxxxxx]
Sent: Sat 12/6/2008 11:53 PM
To: Karen Xie
Cc: linux-scsi@xxxxxxxxxxxxxxx; open-iscsi@xxxxxxxxxxxxxxxx; michaelc@xxxxxxxxxxx; James.Bottomley@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [PATCH 0/3 2.6.29] cxgb3i -- driver fixes & updates
From: Karen Xie <kxie@xxxxxxxxxxx>
Date: Sat, 6 Dec 2008 23:09:36 -0800
It is based on the cxgb3i branch of Mike's linux-2.6-iscsi tree. It needs the
patch Mike sent several days ago on preparing the iscsi core libary for pdu
offload (http://marc.info/?l=linux-scsi&m=122819956917473).
If this dependency exists I probably can't pull this into the
net-next-2.6 then, just FYI but you probably already understand
this :-)
--
To unsubscribe from this list: 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
