From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH v2] nvmet_fc: Add queue create and delete callbacks in LLDD api
Date: Tue, 9 May 2017 09:26:53 +0200 [thread overview]
Message-ID: <f60d818d-3053-1a51-0702-882f59bdd702@suse.de> (raw)
In-Reply-To: <20170508214851.28690-1-jsmart2021@gmail.com>
On 05/08/2017 11:48 PM, jsmart2021@gmail.com wrote:
> From: James Smart <jsmart2021 at gmail.com>
>
> To facilitate LLDD resource management on nvme queue creation and
> deletion, add optional callbacks queue_create and queue_delete.
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> ---
> v2: require queue_delete if queue_create entrypoint present
Thanks,
Reviewed-by: Johannes Thumshirn <jthumshirn at suse.de>
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
prev parent reply other threads:[~2017-05-09 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 21:48 [PATCH v2] nvmet_fc: Add queue create and delete callbacks in LLDD api jsmart2021
2017-05-09 7:26 ` Johannes Thumshirn [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=f60d818d-3053-1a51-0702-882f59bdd702@suse.de \
--to=jthumshirn@suse.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