From: Christoph Hellwig <hch@lst.de>
To: Robert Baldyga <robert.baldyga@intel.com>
Cc: sagi@grimberg.me, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, michal.rakowski@intel.com,
axboe@fb.com, kbusch@kernel.org, hch@lst.de
Subject: Re: [PATCH 0/2] nvme: Add kernel API for admin command
Date: Fri, 13 Sep 2019 16:37:09 +0200 [thread overview]
Message-ID: <20190913143709.GA8525@lst.de> (raw)
In-Reply-To: <20190913111610.9958-1-robert.baldyga@intel.com>
On Fri, Sep 13, 2019 at 01:16:08PM +0200, Robert Baldyga wrote:
> Hello,
>
> This patchset adds two functions providing kernel to kernel API
> for submiting NVMe admin commands. This is for use of NVMe-aware
> block device drivers stacking on top of NVMe drives. An example of
> such driver is Open CAS Linux [1] which uses NVMe extended LBA
> formats and thus needs to issue commands like nvme_admin_identify.
We never add functionality for out of tree crap. And this shit really
is a bunch of crap, so it is unlikely to ever be merged.
Why can't intel sometimes actually do something useful for a change
instead of piling junk over junk?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-09-13 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 11:16 [PATCH 0/2] nvme: Add kernel API for admin command Robert Baldyga
2019-09-13 11:16 ` [PATCH 1/2] nvme: add API for sending admin commands by bdev Robert Baldyga
2019-09-16 6:36 ` kbuild test robot
2019-09-13 11:16 ` [PATCH 2/2] nvme: add API for getting nsid " Robert Baldyga
2019-09-16 6:57 ` kbuild test robot
2019-09-13 14:37 ` Christoph Hellwig [this message]
2019-09-16 7:16 ` [PATCH 0/2] nvme: Add kernel API for admin command Baldyga, Robert
2019-09-16 7:34 ` Christoph Hellwig
2019-09-16 12:13 ` Baldyga, Robert
2019-09-17 16:39 ` Keith Busch
2019-09-18 13:26 ` Christoph Hellwig
2019-09-18 17:08 ` Keith Busch
2019-09-18 17:09 ` Christoph Hellwig
2019-09-19 0:40 ` Martin K. Petersen
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=20190913143709.GA8525@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=michal.rakowski@intel.com \
--cc=robert.baldyga@intel.com \
--cc=sagi@grimberg.me \
/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).