From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/3] nvme: Asynchronous driver commands API
Date: Tue, 30 Jan 2018 08:05:14 +0100 [thread overview]
Message-ID: <20180130070514.GA12196@lst.de> (raw)
In-Reply-To: <20180129235949.26267-2-keith.busch@intel.com>
As pointed our by Roland we'll need to make sure req->cmd is allocated
dynamically for async commands. I suspect the best way to handle that
is to turn it into an actual embedded structure instead of a pointer.
next prev parent reply other threads:[~2018-01-30 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 23:59 [PATCH 1/3] nvme: Sync queues on controller resets Keith Busch
2018-01-29 23:59 ` [PATCH 2/3] nvme: Asynchronous driver commands API Keith Busch
2018-01-30 7:05 ` Christoph Hellwig [this message]
2018-01-29 23:59 ` [PATCH 3/3] nvme-pci: Delete HMB asynchronously Keith Busch
2018-01-30 9:28 ` [PATCH 1/3] nvme: Sync queues on controller resets jianchao.wang
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=20180130070514.GA12196@lst.de \
--to=hch@lst.de \
/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).