From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] nvme: use uuid_t in nvme_ns
Date: Mon, 12 Jun 2017 18:06:02 +0200 [thread overview]
Message-ID: <20170612160602.GB30030@lst.de> (raw)
In-Reply-To: <20170612091240.18343-1-jthumshirn@suse.de>
On Mon, Jun 12, 2017 at 11:12:40AM +0200, Johannes Thumshirn wrote:
> struct nvme_ns still uses u u8 uuid[16], change it to using uuid_t and
> use the UUID API.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Thanks, folded into the two patches originall introducing the code.
next prev parent reply other threads:[~2017-06-12 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 9:12 [PATCH v2] nvme: use uuid_t in nvme_ns Johannes Thumshirn
2017-06-12 9:50 ` Andy Shevchenko
2017-06-12 10:04 ` Johannes Thumshirn
2017-06-12 11:03 ` Christoph Hellwig
2017-06-12 13:11 ` Andy Shevchenko
2017-06-12 16:06 ` Christoph Hellwig [this message]
2017-06-15 8:57 ` Sagi Grimberg
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=20170612160602.GB30030@lst.de \
--to=hch@lst.de \
--cc=andy.shevchenko@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.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