From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH nvme-cli v2 0/2] fabrics connect-all fixes
Date: Thu, 9 Aug 2018 08:59:38 -0600 [thread overview]
Message-ID: <20180809145938.GA18274@localhost.localdomain> (raw)
In-Reply-To: <20180809092523.10225-1-jthumshirn@suse.de>
On Thu, Aug 09, 2018@11:25:21AM +0200, Johannes Thumshirn wrote:
> Two small fixes for fabrics commits of mine, which introduced options
> but forgot to pass them down to the kernel.
Thanks, series applied.
prev parent reply other threads:[~2018-08-09 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 9:25 [PATCH nvme-cli v2 0/2] fabrics connect-all fixes Johannes Thumshirn
2018-08-09 9:25 ` [PATCH nvme-cli v2 1/2] fabrics: write ctrl_loss_tmo to fabrics device on connect Johannes Thumshirn
2018-08-09 9:25 ` [PATCH nvme-cli v2 2/2] fabrics: write keep-alive-timeout " Johannes Thumshirn
2018-08-09 14:59 ` Keith Busch [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=20180809145938.GA18274@localhost.localdomain \
--to=keith.busch@linux.intel.com \
/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.