From: Bart Van Assche <bart.vanassche@sandisk.com>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: target-devel <target-devel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: [LSF/MM TOPIC] LIO/SCST Merger
Date: Wed, 27 Jan 2016 09:54:03 -0800 [thread overview]
Message-ID: <56A9043B.7030207@sandisk.com> (raw)
Last year, during the 2015 LSF/MM summit, it has been decided that the
LIO/SCST merger project should proceed by sending the functionality
upstream that is present in SCST but not yet in LIO. This will help to
reduce the workload of target driver maintainers that maintain a version
of their target driver for both LIO and SCST (QLogic FC and FCoE target
drivers, Emulex FC and FCoE target drivers, RDMA iSER target driver,
RDMA SRP target driver, ...). My proposal is to organize a session
during which the following is discussed:
* Which patches are already upstream in the context of the LIO/SCST
merger project.
* About which patches there is agreement but that are not yet upstream.
* To discuss how to proceed from here and what to address first.
References:
[1] Bart Van Assche, [LSF/MM TOPIC] Unifying the LIO and SCST target
drivers, January 2015
(http://thread.gmane.org/gmane.linux.scsi.target.devel/7779)
[2] James Bottomley, LIO/SCST merger, April 2015
(https://plus.google.com/112086662098298535411/posts/HuGsCMU41uy).
next reply other threads:[~2016-01-27 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 17:54 Bart Van Assche [this message]
2016-01-27 18:08 ` [Lsf-pc] [LSF/MM TOPIC] LIO/SCST Merger James Bottomley
2016-01-27 18:19 ` Bart Van Assche
2016-01-27 18:31 ` James Bottomley
2016-01-28 6:36 ` Nicholas A. Bellinger
2016-01-28 9:01 ` Christoph Hellwig
2016-01-28 16:24 ` Sagi Grimberg
2016-01-28 16:47 ` [Lsf-pc] " James Bottomley
2016-01-28 15:34 ` Bart Van Assche
2016-02-01 2:44 ` Alex Gorbachev
2016-01-29 2:57 ` Vladislav Bolkhovitin
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=56A9043B.7030207@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).