From: emilne@redhat.com (Ewan D. Milne)
Subject: [PATCH] nvme-fc: initialize nvme_req(rq)->ctrl after calling __nvme_fc_init_request()
Date: Mon, 26 Nov 2018 16:31:12 -0500 [thread overview]
Message-ID: <181e9cb49b93d6119b0d5ee8651c1b3e10c6d08c.camel@redhat.com> (raw)
In-Reply-To: <20181126212617.12269-1-emilne@redhat.com>
On Mon, 2018-11-26@16:26 -0500, Ewan D. Milne wrote:
>
My apologies, duplicate email.
-Ewan
next prev parent reply other threads:[~2018-11-26 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 21:26 [PATCH] nvme-fc: initialize nvme_req(rq)->ctrl after calling __nvme_fc_init_request() Ewan D. Milne
2018-11-26 21:31 ` Ewan D. Milne [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-26 17:01 Ewan D. Milne
2018-11-26 19:45 ` Hannes Reinecke
2018-11-27 7:35 ` Christoph Hellwig
2018-11-27 17:07 ` James Smart
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=181e9cb49b93d6119b0d5ee8651c1b3e10c6d08c.camel@redhat.com \
--to=emilne@redhat.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.