Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK support for NVMe CMBs and PMRs with WDS/RDS
Date: Thu, 08 Feb 2018 05:07:48 +0000	[thread overview]
Message-ID: <D3BBC909-0FB9-430A-BE01-C32324F8C84C@intel.com> (raw)
In-Reply-To: FF7FC980937D6342B9D289F5F3C7C2625B60E801@SHSMSX103.ccr.corp.intel.com

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

Hey Stephen,

Sorry for the unrelated test failure – as expected it passed the second time.

Overall the patch series looks good – I just reviewed the whole patch series and added some comments.  Appreciate you taking the time to add the cmb_copy example app!

Thanks,

-Jim


On 2/7/18, 8:05 PM, "SPDK on behalf of Liu, Changpeng" <spdk-bounces(a)lists.01.org on behalf of changpeng.liu(a)intel.com> wrote:

    Hi Stephen,
    
    I removed the -1 label, will start a new round test soon.
    
    > -----Original Message-----
    > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Stephen Bates
    > Sent: Thursday, February 8, 2018 10:35 AM
    > To: Storage Performance Development Kit <spdk(a)lists.01.org>
    > Subject: Re: [SPDK] SPDK support for NVMe CMBs and PMRs with WDS/RDS
    > 
    > > My v2 for the NVMe CMB WDS/RDS enablement is now up for review.
    > 
    > So I see my v2 series got pulled into the CI system. It *looks* like an unrelated
    > change is causing one test system to fail. I don't think my changes are causing
    > this failure but I'd appreciate it if someone with more experience could check
    > that.
    > 
    > https://ci.spdk.io/spdk/builds/review/d70dda617b40d8c099eef8313f5b959c0153
    > 0d3e.1518046779/fedora-08/
    > 
    > This is the 3rd patch in the 5 patch series. I see patches 4 and 5 are getting clean
    > bills of health for the same tests. Does the CI tool apply each patch in turn and
    > then run its tests (I assume it must as patches 4 and 5 depend on the prior
    > patches).
    > 
    > Cheers
    > 
    > Stephen
    > 
    > 
    > 
    > _______________________________________________
    > SPDK mailing list
    > SPDK(a)lists.01.org
    > https://lists.01.org/mailman/listinfo/spdk
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    


             reply	other threads:[~2018-02-08  5:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08  5:07 Harris, James R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-09  0:29 [SPDK] SPDK support for NVMe CMBs and PMRs with WDS/RDS Stephen Bates
2018-02-09  0:07 Stephen Bates
2018-02-08 23:46 Harris, James R
2018-02-08 23:36 Stephen Bates
2018-02-08  5:17 Stephen Bates
2018-02-08  3:05 Liu, Changpeng
2018-02-08  2:35 Stephen Bates
2018-02-07 23:18 Stephen Bates
2018-02-07 18:53 Stephen Bates
2018-02-07  0:20 Harris, James R
2018-02-06  4:05 Harris, James R
2018-02-06  3:06 Stephen Bates
2018-02-01 22:04 Stephen Bates
2018-01-31 21:43 Walker, Benjamin
2018-01-31 20:14 Harris, James R
2018-01-31 20:08 Stephen Bates
2018-01-30  8:45 Stojaczyk, DariuszX
2018-01-30  3:35 Stephen Bates

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=D3BBC909-0FB9-430A-BE01-C32324F8C84C@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox