From: Christoph Hellwig <hch@lst.de>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs <linux-xfs@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 2/3] xfs: use uuid_be to implement the uuid_t type
Date: Fri, 5 May 2017 10:48:13 +0200 [thread overview]
Message-ID: <20170505084813.GA4805@lst.de> (raw)
In-Reply-To: <CAOQ4uxg=wLW9d195W_Ro71iNZEt8jVFyVwXysd-WnuDx7ELKDw@mail.gmail.com>
On Fri, May 05, 2017 at 11:44:16AM +0300, Amir Goldstein wrote:
> How about moving this typedef to linux/uuid.h.
Yes, I think eventually we want that, but for now I tried to keep
it local to XFS. uuid.h already is a mess with uuid_be/uuid_le and
struct uuid_v1.
I think I'll need to do a series on that first, but this might
run into conflicts with the work that Andy is doing at the moment.
> It's weird to have a non xfs_ prefixed typedef as it was
> and placing it here is even more weird.
We do have a few typedefs like that, but maybe we should eventually
clean them up.
> Yes, only xfs uses uuid_t right now, but this could mark the intentions
> in a central place, so other code can follow suit (i.e. libnvdimm) and
> start using uuid_t as well.
I think libnvdimm would be guid_t.
> If this is acceptable by Andy, I can re-post my series based on top
> of this one to hoist uuid_t and the rest of the xfs helpers to linux/uuid.h.
Sure. There actually are very few users of uuid_be at the moment,
so it might be a good opportunity to just kill if off ASAP.
uuid_le might take a little more time if it's really worth it.
next prev parent reply other threads:[~2017-05-05 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 7:57 XFS UUID cleanups Christoph Hellwig
2017-05-05 7:57 ` [PATCH 1/3] xfs: use uuid_copy() helper to abstract uuid_t Christoph Hellwig
2017-05-05 7:57 ` [PATCH 2/3] xfs: use uuid_be to implement the uuid_t type Christoph Hellwig
2017-05-05 8:44 ` Amir Goldstein
2017-05-05 8:48 ` Christoph Hellwig [this message]
2017-05-05 9:42 ` Andy Shevchenko
2017-05-05 9:56 ` Christoph Hellwig
2017-05-05 10:06 ` Andy Shevchenko
2017-05-05 10:10 ` Christoph Hellwig
2017-05-10 8:39 ` Amir Goldstein
2017-05-10 12:01 ` Christoph Hellwig
2017-05-10 12:54 ` Andy Shevchenko
2017-05-10 14:15 ` Christoph Hellwig
2017-05-05 7:57 ` [PATCH 3/3] xfs: remove uuid_getnodeuniq and xfs_uu_t Christoph Hellwig
2017-05-05 8:27 ` Amir Goldstein
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=20170505084813.GA4805@lst.de \
--to=hch@lst.de \
--cc=amir73il@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-xfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).