From: Keith Busch <kbusch@kernel.org>
To: Tony Asleson <tasleson@redhat.com>
Cc: linux-nvme@lists.infradead.org, Tomas Bzatek <tbzatek@redhat.com>
Subject: Re: libnvme questions
Date: Wed, 10 Mar 2021 12:48:44 -0800 [thread overview]
Message-ID: <20210310204844.GC3377333@dhcp-10-100-145-180.wdc.com> (raw)
In-Reply-To: <245fc813-9441-56d8-47e2-4417fc1f87e7@redhat.com>
On Wed, Mar 03, 2021 at 03:14:02PM -0600, Tony Asleson wrote:
> 1. There is interest in utilizing the libnvme library for some other
> projects, when is an official release of the library planned?
>
> 2. Is it planned for nvme-cli to utilize libnvme?
This is my bad, I fell behind the task due to mutliple conflicts of
time, but I am back on this right now. The plan is to tag nvme-cli v1.14
within the next few weeks, then make the shift to libnvme integration
on a "2.0" version for future work on the master branch. This would
coincide with an official libnvme stable release.
I honestly do not have enough devices to regression test all the
features, so I will continue to maintain nvme-cli 1.x branches as long
as necessary while ironing out any integration issues.
> 3. Any plans on adding functionality for NVMe management interfaces to
> the library, e.g. NVMe Enclosures?
Will be happen to incorporate any features that are in-spec.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-03-10 20:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:14 libnvme questions Tony Asleson
2021-03-08 7:48 ` Chaitanya Kulkarni
2021-03-10 20:48 ` Keith Busch [this message]
2021-03-11 4:43 ` Chaitanya Kulkarni
2021-03-12 15:35 ` Tony Asleson
2021-03-12 16:18 ` Keith Busch
[not found] ` <CGME20210407123854epcas5p48217db953741a57d651a8a8bf240ee23@epcas5p4.samsung.com>
2021-04-07 12:38 ` Padmakar Kalghatgi
2021-04-07 23:16 ` Chaitanya Kulkarni
2021-04-08 7:48 ` Padmakar Kalghatgi
2021-04-09 3:58 ` Chaitanya Kulkarni
2021-04-09 5:48 ` Klaus Jensen
2021-04-12 11:48 ` Padmakar Kalghatgi
2021-04-07 23:19 ` Chaitanya Kulkarni
2021-04-08 7:50 ` Padmakar Kalghatgi
2021-04-07 23:37 ` Keith Busch
2021-04-08 7:51 ` Padmakar Kalghatgi
2021-04-08 16:46 ` Keith Busch
2021-04-12 8:56 ` Padmakar Kalghatgi
2021-04-08 12:09 ` Christoph Hellwig
2021-03-31 14:15 ` Hannes Reinecke
2021-03-31 14:54 ` Keith Busch
2021-03-31 15:29 ` Hannes Reinecke
2021-04-07 21:34 ` Keith Busch
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=20210310204844.GC3377333@dhcp-10-100-145-180.wdc.com \
--to=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=tasleson@redhat.com \
--cc=tbzatek@redhat.com \
/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).