From: James Smart <jsmart2021@gmail.com>
To: linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org
Cc: James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH v2] lpfc: Tie in to new dev_loss_tmo interface in nvme transport
Date: Fri, 3 Nov 2017 09:33:00 -0700 [thread overview]
Message-ID: <a88fe08e-5393-a1c7-bfa7-fa2614517179@gmail.com> (raw)
In-Reply-To: <20171103163040.28344-1-jsmart2021@gmail.com>
sorry or the noise. disregard. didn't pick up the chg
prev parent reply other threads:[~2017-11-03 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 16:30 [PATCH v2] lpfc: Tie in to new dev_loss_tmo interface in nvme transport James Smart
2017-11-03 16:33 ` James Smart [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=a88fe08e-5393-a1c7-bfa7-fa2614517179@gmail.com \
--to=jsmart2021@gmail.com \
--cc=james.smart@broadcom.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).