From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 1/7] nvme-fabrics: Add FC transport FC-NVME definitions
Date: Wed, 5 Oct 2016 09:29:32 +0300 [thread overview]
Message-ID: <73381327-38b4-ba27-d071-439212b4018a@grimberg.me> (raw)
In-Reply-To: <20161004135825.GB23761@infradead.org>
Hay James,
I'm not sure why, but the original patchset from you
doesn't appear in my mailbox. Can you please either:
- provide a pull location and/or
- resend with cc'ing sagi at grimberg.me so I can also
provide feedback? (or simply git send me the series
and I'll include linux-nvme on relevant feedback which
will avoid spamming linux-nvme).
Sorry and thanks,
Sagi.
next prev parent reply other threads:[~2016-10-05 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 6:26 [PATCH 1/7] nvme-fabrics: Add FC transport FC-NVME definitions James Smart
2016-10-04 7:32 ` Hannes Reinecke
2016-10-04 13:58 ` Christoph Hellwig
2016-10-05 6:29 ` Sagi Grimberg [this message]
2016-10-05 23:21 ` James Smart
2016-10-06 6:31 ` Hannes Reinecke
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=73381327-38b4-ba27-d071-439212b4018a@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.