From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet-rdma: Fix REJ status code
Date: Wed, 19 Oct 2016 12:34:23 +0200 [thread overview]
Message-ID: <20161019103423.GC525@lst.de> (raw)
In-Reply-To: <10b8f472-ea1b-5449-e24a-f6bbee8a4d54@sandisk.com>
On Tue, Oct 18, 2016@12:59:47PM -0700, Bart Van Assche wrote:
> nvmet_sq_init() returns a value <= 0. nvmet_rdma_cm_reject() expects
> a second argument that is a NVME_RDMA_CM_* constant. Hence this patch.
>
> Signed-off-by: Bart Van Assche <bart.vanassche at sandisk.com>
Looks fine,
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2016-10-19 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 19:59 [PATCH] nvmet-rdma: Fix REJ status code Bart Van Assche
2016-10-19 10:34 ` Christoph Hellwig [this message]
2016-10-20 8:03 ` Sagi Grimberg
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=20161019103423.GC525@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.