From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Amir Goldstein <amir73il@gmail.com>, Christoph Hellwig <hch@lst.de>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Richard Weinberger <richard@nod.at>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Mark Fasheh <mfasheh@versity.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-unionfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
David Howells <dhowells@redhat.com>, Theodore Tso <tytso@mit.edu>
Subject: Re: [RFC][PATCH] linux/uuid.h: hoist uuid_is_null() helper from libnvdimm
Date: Wed, 03 May 2017 20:15:47 +0300 [thread overview]
Message-ID: <1493831747.30052.10.camel@linux.intel.com> (raw)
In-Reply-To: <1493829352.30052.6.camel@linux.intel.com>
On Wed, 2017-05-03 at 19:35 +0300, Andy Shevchenko wrote:
> On Wed, 2017-05-03 at 15:42 +0300, Amir Goldstein wrote:
> > On Wed, May 3, 2017 at 2:00 PM, Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Wed, 2017-05-03 at 13:05 +0300, Amir Goldstein wrote:
> > > > On Wed, May 3, 2017 at 12:13 PM, Andy Shevchenko
> > I can hear the voices of
> > > > those saying that there should be a 'natural' helper
> > > > uuid_is_null(u8
> > > > *) for the
> > > > users that represent uuid as u8[16] (i.e. filesystems and sb-
> > > > > s_uuid).
> > >
> > > u8 * doesn't represent UUID as a type.
> > > Perhaps we need to reflect this in the name of the function
> > > somehow.
> > >
> >
> > OK, since you have no time nor the intention to convert filesystem
> > code
> > to use uuid_le
>
> uuid_be I suppose. I noticed core developers doesn't support endianess
> feature of UUID: https://lkml.org/lkml/2016/5/25/724
>
> That's also why I don't want to touch filesystem stuff.
>
> > (not should you), I see 2 options for filesystems/VFS:
> >
> > 1. Use the simple u8* libnvdimm helper proposed by this patch
> > 2. Hoist uuid_t + helpers from fs/xfs/uuid.* to linux/uuid.h
> > lib/uuid.c
> >
> > If option #2 is preferred, I think we should conform to libuuid's
> > helper
> > name uuid_is_null() (instead of freebsd's uuid_is_nil())
I renamed as proposed and updated my branch.
By the way, notice that uuid_v1 type (which had been moved to uuid.h
already) is the same what xfs uses as uuid_t.
So, helpers against it we can prefix with uuid_v1_[foo_bar()].
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-05-03 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 20:19 [RFC][PATCH] linux/uuid.h: hoist uuid_is_null() helper from libnvdimm Amir Goldstein
2017-05-02 20:57 ` Dan Williams
2017-05-03 9:13 ` Andy Shevchenko
2017-05-03 10:05 ` Amir Goldstein
2017-05-03 11:00 ` Andy Shevchenko
2017-05-03 12:42 ` Amir Goldstein
2017-05-03 16:35 ` Andy Shevchenko
2017-05-03 17:15 ` Andy Shevchenko [this message]
2017-05-03 18:34 ` Amir Goldstein
2017-05-04 8:21 ` Andy Shevchenko
2017-05-04 8:39 ` 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=1493831747.30052.10.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=amir73il@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mfasheh@versity.com \
--cc=miklos@szeredi.hu \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.vnet.ibm.com \
/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.