linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: linux-block@vger.kernel.org, "Matias Bjørling" <matias.bjorling@wdc.com>
Subject: Re: [PATCH 0/4] lightnvm pull request
Date: Tue, 13 Apr 2021 09:16:56 -0600	[thread overview]
Message-ID: <b98f19e9-bfda-fb61-fa56-c41d69d56edc@kernel.dk> (raw)
In-Reply-To: <20210413105257.159260-1-matias.bjorling@wdc.com>

On 4/13/21 4:52 AM, Matias Bjørling wrote:
> Hi Jens,
> 
> Please pick up when convenient.
> 
> This PR officially deprecates the lightnvm subsystem and prepares
> it to be removed from kernel 5.15 and onward.
> 
> The lightnvm subsystem has been superseeded by the recently standardized
> NVMe Zoned Namespace (ZNS) Command Set specification. Together with other
> advancements in NVMe, it is now possible to implement all of the features that
> the original OCSSD work introduced.
> 
> Thanks for enabling me to contribute the subsystem. It has been an incredible
> journey. While the subsystem itself had not had that many users outside of
> academia and initial PoCs, it has been instrumental in gaining
> enough mind-share in the industry, which ultimately has allowed ZNS SSDs to
> emerge. Thank you!

Applied, thanks.

-- 
Jens Axboe


      parent reply	other threads:[~2021-04-13 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 10:52 [PATCH 0/4] lightnvm pull request Matias Bjørling
2021-04-13 10:52 ` [PATCH 1/4] lightnvm: use kobj_to_dev() Matias Bjørling
2021-04-13 10:52 ` [PATCH 2/4] lightnvm: return the correct return value Matias Bjørling
2021-04-13 10:52 ` [PATCH 3/4] lightnvm: remove duplicate include in lightnvm.h Matias Bjørling
2021-04-13 10:52 ` [PATCH 4/4] lightnvm: deprecated OCSSD support and schedule it for removal in Linux 5.15 Matias Bjørling
2021-04-13 15:16 ` Jens Axboe [this message]

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=b98f19e9-bfda-fb61-fa56-c41d69d56edc@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=matias.bjorling@wdc.com \
    --cc=mb@lightnvm.io \
    /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).