From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvmet: Add support for HOST_ID feature.
Date: Tue, 29 Aug 2017 01:32:00 -0700 [thread overview]
Message-ID: <20170829083200.GA30908@infradead.org> (raw)
In-Reply-To: <9f119f3b-cca9-7c6e-64ff-53bd24249de3@grimberg.me>
On Mon, Aug 28, 2017@11:15:57PM +0300, Sagi Grimberg wrote:
> That's true, We should work with uuid_t for hostids. thanks Daniel.
And we already do on the host side, it's just that the target didn't
need to parse it yet.
next prev parent reply other threads:[~2017-08-29 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 12:07 [PATCH] nvmet: Add support for HOST_ID feature Omri Mann
2017-08-28 13:43 ` Sagi Grimberg
2017-08-28 18:10 ` Verkamp, Daniel
2017-08-28 20:15 ` Sagi Grimberg
2017-08-29 8:32 ` Christoph Hellwig [this message]
2017-08-28 14:36 ` Christoph Hellwig
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=20170829083200.GA30908@infradead.org \
--to=hch@infradead.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