[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170518071352.GA515@lst.de>
Date: Thu, 18 May 2017 09:13:52 +0200
From: Christoph Hellwig <hch@....de>
To: Joe Perches <joe@...ches.com>
Cc: Christoph Hellwig <hch@....de>,
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>,
David Howells <dhowells@...hat.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
Subject: Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi
header
On Thu, May 18, 2017 at 12:12:45AM -0700, Joe Perches wrote:
> On Thu, 2017-05-18 at 08:26 +0200, Christoph Hellwig wrote:
> > We don't use uuid_be and the UUID_BE constants in any uapi headers, so make
> > them private to the kernel.
>
> On the assumption that no user program uses them?
> Is that a safe assumption?
It's not a userspace ABI, so by defintion it does not break an
existing user program. If someone was using it they should be using
uuid_t from libuuid instead, as that gives them the routines to deal
with it.
Powered by blists - more mailing lists