[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13041.1495191521@warthog.procyon.org.uk>
Date: Fri, 19 May 2017 11:58:41 +0100
From: David Howells <dhowells@...hat.com>
To: Christoph Hellwig <hch@....de>
Cc: dhowells@...hat.com, Joe Perches <joe@...ches.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Amir Goldstein <amir73il@...il.com>,
linux-fsdevel@...r.kernel.org, Shaohua Li <shli@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
linux-xfs@...r.kernel.org, linux-raid@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org
Subject: Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header
Christoph Hellwig <hch@....de> wrote:
> It's not a userspace ABI, so by defintion it does not break an
> existing user program.
That's an invalid assumption. It is a de facto userspace ABI as it has been
exposed in /usr/include/linux/uuid.h for some time.
> If someone was using it they should be using uuid_t from libuuid instead, as
> that gives them the routines to deal with it.
Yes, they should - but that doesn't mean they do.
David
Powered by blists - more mailing lists