From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
"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: Re: [Lsf-pc] [LSF/MM TOPIC] LIO/SCST Merger
Date: Wed, 27 Jan 2016 10:08:24 -0800 [thread overview]
Message-ID: <1453918104.2322.26.camel@HansenPartnership.com> (raw)
In-Reply-To: <56A9043B.7030207@sandisk.com>
On Wed, 2016-01-27 at 09:54 -0800, Bart Van Assche wrote:
> 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.
Can you begin this in email ... I don't think any of us are clear if
there's still an issue here ... or that we'd say more than send the
patches upstream, like we did last year. Just reporting on patch
status isn't that useful ... if there were design disputes or issues to
discuss that caused the patches not to be accepted, that would be more
useful.
James
next prev parent reply other threads:[~2016-01-27 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 17:54 [LSF/MM TOPIC] LIO/SCST Merger Bart Van Assche
2016-01-27 18:08 ` James Bottomley [this message]
2016-01-27 18:19 ` [Lsf-pc] " 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=1453918104.2322.26.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=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).