From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH nvme-cli] Documentation: add manpage entry for connect's --ctrl-loss-tmo setting
Date: Wed, 18 Apr 2018 08:25:47 -0600 [thread overview]
Message-ID: <20180418142547.GK11513@localhost.localdomain> (raw)
In-Reply-To: <SN6PR06MB3984E543C38C05F4E379100D8CB60@SN6PR06MB3984.namprd06.prod.outlook.com>
On Wed, Apr 18, 2018@02:21:47PM +0000, Schremmer, Steven wrote:
> > Sent: Tuesday, April 10, 2018 12:26 PM
> > To: Johannes Thumshirn <jthumshirn at suse.de>
> > Cc: Schulte, Matt <Matt.Schulte at netapp.com>; Linux NVMe Mailinglist <linux-nvme at lists.infradead.org>
> > Subject: Re: [PATCH nvme-cli] Documentation: add manpage entry for connect's --ctrl-loss-tmo setting
> >
> > Thanks, applied.
> >
>
> Keith, I'm not seeing this patch on github. Can you double check that it got applied?
Oops, thanks for the notice. In my haste, I didn't see the push failed
and needed to merge. Should be there now.
prev parent reply other threads:[~2018-04-18 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 8:51 [PATCH nvme-cli] Documentation: add manpage entry for connect's --ctrl-loss-tmo setting Johannes Thumshirn
2018-04-10 17:25 ` Keith Busch
2018-04-18 14:21 ` Schremmer, Steven
2018-04-18 14:25 ` 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=20180418142547.GK11513@localhost.localdomain \
--to=keith.busch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox