From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Libnotify release plans
Date: Mon, 22 Apr 2019 19:25:46 +0000 [thread overview]
Message-ID: <ff62f5f798fbac7bb077346c160d74ee72ba996e.camel@intel.com> (raw)
In-Reply-To: CANvN+ekjcO4xm10xgiMDeZrW85nXZ-r-YwwMGMrOx9-7bmZunw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Mon, 2019-04-22 at 16:49 +0300, Andrey Kuzmin wrote:
> Has libnotify been scheduled for any upcoming spdk release? If not, what
> are the actual release plans for the notification library?
This has been merged for 19.04. There are some patches outstanding to begin to
use it (specifically in spdkcli) that may or may not make the release, but the
core library and functionality is all merged.
>
> Thanks,
> Andrey
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-04-22 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 19:25 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-22 20:06 [SPDK] Libnotify release plans Andrey Kuzmin
2019-04-22 18:18 Luse, Paul E
2019-04-22 18:14 Andrey Kuzmin
2019-04-22 15:39 Luse, Paul E
2019-04-22 13:49 Andrey Kuzmin
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=ff62f5f798fbac7bb077346c160d74ee72ba996e.camel@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