From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 1/1] nvmet-rdma: Add an error flow for post_recv failures
Date: Mon, 2 Jul 2018 15:16:10 +0200 [thread overview]
Message-ID: <20180702131610.GF4624@lst.de> (raw)
In-Reply-To: <1530436824-18229-1-git-send-email-maxg@mellanox.com>
On Sun, Jul 01, 2018@12:20:24PM +0300, Max Gurtovoy wrote:
> Posting receive buffer operation can fail, thus we should make
> sure to have an error flow during initialization phase. While
> we're here, add a debug print in case of a failure.
>
> Signed-off-by: Max Gurtovoy <maxg at mellanox.com>
Looks fine to me. Do you see an urgent enough issue to queue this
up for 4.18 or can it wait for 4.19?
next prev parent reply other threads:[~2018-07-02 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 9:20 [PATCH v2 1/1] nvmet-rdma: Add an error flow for post_recv failures Max Gurtovoy
2018-07-02 13:16 ` Christoph Hellwig [this message]
2018-07-02 15:21 ` Max Gurtovoy
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=20180702131610.GF4624@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