From: sagi@grimberg.me (Sagi Grimberg)
Subject: Status of "nvmet: Add feature close connection from target side"
Date: Thu, 1 Mar 2018 11:14:43 +0200 [thread overview]
Message-ID: <f13d2d21-c828-dd07-486e-1b4069c9e7da@grimberg.me> (raw)
In-Reply-To: <CAF9HSim=BXt_nFEGYs_yzzcdQyxsw2+pK6X-ZNo9Wr-f2AubJg@mail.gmail.com>
> Hi,
>
> A set of patches was submitted to the mailing list on Oct 10 by
> israelr at mellanox.com.
> In terms of due process, what should be done in order to merge the
> feature upstream? we'd be happy to contribute.
Patches 3,4 had some feedback that wasn't addressed iirc.
prev parent reply other threads:[~2018-03-01 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 7:52 Status of "nvmet: Add feature close connection from target side" Alon Horev
2018-03-01 9:14 ` Sagi Grimberg [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=f13d2d21-c828-dd07-486e-1b4069c9e7da@grimberg.me \
--to=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 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.