From: Luse, Paul E <paul.e.luse at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Bug fixes for SPDK 19.01.1 release
Date: Tue, 26 Feb 2019 02:33:19 +0000 [thread overview]
Message-ID: <82C9F782B054C94B9FC04A331649C77AB8CEAC8D@FMSMSX126.amr.corp.intel.com> (raw)
In-Reply-To: 17AD763A69C1A24CA48C89AF5671662088600BE3@SHSMSX101.ccr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 1994 bytes --]
Just FYI for everyone... BKC stands for "Best Known Configuration" and is extra testing we do above and beyond the community infrastructure in conjunction with the Intel SSD folks - it allows them (and us) to test SPDK with pre-release SSDs helping to assure the best possible experience for everyone :)
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Wan, Qun
Sent: Monday, February 25, 2019 7:05 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Bug fixes for SPDK 19.01.1 release
Hi, Tomek
Thank you for the info. This is quite helpful, just one question, as BKC has a issue when running with vhost and Jim has a patch merged into the master, I checked it's not taged with 19.01.1 yet, I guess it should be added into the 19.01.1 release. Patch link as follows https://review.gerrithub.io/#/c/spdk/spdk/+/445764/
Best Regards,
Anna
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Zawadzki, Tomasz
Sent: Monday, February 25, 2019 11:09 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Bug fixes for SPDK 19.01.1 release
Hello all,
We are preparing for SPDK 19.01.1 release, which will contain critical bug fixes that were merged since release of SPDK 19.01.
Patches to be backported to 19.01.x branch need to be present in SPDK master first.
Please let us know if there are any important bug fixes that should be backported by adding "19.01.1" hashtag to the patch or replying to this thread.
Link for list of backporting candidates:
https://review.gerrithub.io/#/q/hashtag:%2219.01.1%22
Thank you,
Tomek
_______________________________________________
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
next reply other threads:[~2019-02-26 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 2:33 Luse, Paul E [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-26 2:04 [SPDK] Bug fixes for SPDK 19.01.1 release Wan, Qun
2019-02-25 15:09 Zawadzki, Tomasz
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=82C9F782B054C94B9FC04A331649C77AB8CEAC8D@FMSMSX126.amr.corp.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.