All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] RFC patch for NVMe-OF FC transport
Date: Mon, 19 Nov 2018 21:23:56 +0000	[thread overview]
Message-ID: <CAB29699-CA54-4FAE-A86F-0C6FB4FBACAF@intel.com> (raw)
In-Reply-To: CAH1atHQ7y2z9_WpbuR5NSHFsYc7DjJaNkO=rvFMDi3Jj88Jbwg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hi John,

Thanks!

One thing I'm not seeing yet is how NVMe FC will be tested within the automated SPDK CI system.  I would expect test systems in place which would run FC functional tests on each SPDK patch and report results into GerritHub.  The tests that these systems are running should also be checked into the main SPDK repository and plumbed into the autotest.sh framework.

Does Broadcom have plans to add these tests and test systems?

Regards,

-Jim


On 11/16/18, 3:40 PM, "SPDK on behalf of John Barnard" <spdk-bounces(a)lists.01.org on behalf of john.barnard(a)broadcom.com> wrote:

    Hi Ben, Jim, et. al.
    
    I have pushed a patch for review (
    https://review.gerrithub.io/c/spdk/spdk/+/433685) containing the updates to
    add support for Fibre Channel in the  SPDK target NVME-OF transport.
    Please review and comment.  Once we agree on it, I will push a merge patch.
    
    Thanks,
    John
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    


             reply	other threads:[~2018-11-19 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 21:23 Harris, James R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-26 16:34 [SPDK] RFC patch for NVMe-OF FC transport John Barnard
2018-11-16 22:40 John Barnard

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=CAB29699-CA54-4FAE-A86F-0C6FB4FBACAF@intel.com \
    --to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.