From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "jsmart2021@gmail.com" <jsmart2021@gmail.com>,
"herbszt@gmx.de" <herbszt@gmx.de>,
"nab@linux-iscsi.org" <nab@linux-iscsi.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Subject: Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct
Date: Mon, 6 Mar 2017 17:53:04 +0000 [thread overview]
Message-ID: <1488822771.3125.1.camel@sandisk.com> (raw)
In-Reply-To: <20170305173528.00006b41@gmx.de>
On Sun, 2017-03-05 at 17:35 +0100, Sebastian Herbszt wrote:
> Just like Hannes I do favour integration. I guess it could be
> comparable to qla2xxx + tcm_qla2xxx, lpfc + lpfc_scst and
> lpfc + tcm_lpfc. That approach might even help Bart with his
> target driver unification if he didn't give up on that topic.
Hello Sebastian,
That project is still on my to-do list :-) However, while I was
working on that project I hit bugs related to abort handling in
the QLogic FC and also in the iSCSI target drivers. I want to fix
these bugs first because otherwise if my tests fail it is not
possible to figure out whether I hit a regression or an existing
bug.
Bart.
next prev parent reply other threads:[~2017-03-06 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 23:28 [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct James Smart
2017-02-28 16:34 ` Hannes Reinecke
2017-02-28 18:14 ` James Smart
2017-03-01 9:40 ` Hannes Reinecke
2017-03-02 20:08 ` Nicholas A. Bellinger
2017-03-05 16:35 ` Sebastian Herbszt
2017-03-06 17:53 ` Bart Van Assche [this message]
2017-05-16 19:59 ` Roland Dreier
2017-06-12 23:08 ` James Smart
2017-06-13 6:31 ` Christoph Hellwig
2017-06-13 8:29 ` Johannes Thumshirn
2017-06-13 15:34 ` Martin K. Petersen
2017-06-14 11:40 ` Hannes Reinecke
2017-06-14 20:02 ` Sebastian Herbszt
2017-06-16 6:38 ` Hannes Reinecke
2017-03-17 0:10 ` Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1488822771.3125.1.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=herbszt@gmx.de \
--cc=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).