Thanks for the response, Martin.
On Wed, 30 Nov 2016, 8:45am, Martin K. Petersen wrote:
> > "Arun" == Arun Easi writes:
>
> Arun,
>
> Arun> So far, we have been posting qedi changes split into functional
> Arun> blocks, for review, but was not bisectable. With Martin ok to our
> Arun> requ
> "Arun" == Arun Easi writes:
Arun,
Arun> So far, we have been posting qedi changes split into functional
Arun> blocks, for review, but was not bisectable. With Martin ok to our
Arun> request to squash all patches while committing to tree, we were
Arun> wondering if we should post the qedi p
Hi David,
As we are preparing to post V3 of the qed (drivers/net/) and qedi
(drivers/scsi/), I would like to get your opinion on the "qedi" part. As
qedi (the iSCSI driver) is dependent on the accompanying "qed" changes,
qedi changes have to follow or be together with qed changes. Martin is ok
> "Arun" == Arun Easi writes:
Arun,
Arun> Do you have any preference or thoughts on how the "qed" patches be
Arun> approached? Just as a reference, our rdma driver "qedr" went
Arun> through something similar[1], and eventually "qed" patches were
Arun> taken by David in the net tree and "qedr
Hi Martin, David,
This is regarding the submission of the recent patch series we have posted
to linux-scsi and netdev:
[PATCH v2 0/6] Add QLogic FastLinQ iSCSI (qedi) driver.
[PATCH v2 1/6] qed: Add support for hardware offloaded iSCSI.
[PATCH v2 2/6] qed: Add iSCSI out of order packe
