From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Matias Bjorling <mb@lightnvm.io>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1] : Switch to use new generic UUID API
Date: Thu, 10 Jan 2019 16:30:51 +0200 [thread overview]
Message-ID: <20190110143051.52305-1-andriy.shevchenko@linux.intel.com> (raw)
There are new types and helpers that are supposed to be used in new code.
As a preparation to get rid of legacy types and API functions do
the conversion here.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/lightnvm/pblk.h | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/lightnvm/pblk.h b/drivers/lightnvm/pblk.h
index 85e38ed62f85..0a0aeb6ef314 100644
--- a/drivers/lightnvm/pblk.h
+++ b/drivers/lightnvm/pblk.h
@@ -1362,10 +1362,7 @@ static inline unsigned int pblk_get_secs(struct bio *bio)
static inline void pblk_setup_uuid(struct pblk *pblk)
{
- uuid_le uuid;
-
- uuid_le_gen(&uuid);
- memcpy(pblk->instance_uuid, uuid.b, 16);
+ guid_gen((guid_t *)&pblk->instance_uuid);
}
static inline char *pblk_disk_name(struct pblk *pblk)
--
2.20.1
next reply other threads:[~2019-01-10 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 14:30 Andy Shevchenko [this message]
2019-01-21 8:47 ` [PATCH v1] : Switch to use new generic UUID API Christoph Hellwig
2019-01-24 12:16 ` Andy Shevchenko
2019-01-24 13:17 ` Javier González
2019-01-24 13:36 ` Andy Shevchenko
2019-01-24 13:45 ` Javier González
2019-01-24 14:13 ` Andy Shevchenko
2019-01-24 14:36 ` Javier González
2019-01-24 16:38 ` Andy Shevchenko
2019-01-24 16:41 ` Javier González
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=20190110143051.52305-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
/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).