* Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header [not found] ` <20170518071352.GA515-jcswGhMUV9g@public.gmane.org> @ 2017-05-19 10:58 ` David Howells [not found] ` <13041.1495191521-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org> 0 siblings, 1 reply; 2+ messages in thread From: David Howells @ 2017-05-19 10:58 UTC (permalink / raw) To: Christoph Hellwig Cc: linux-xfs-u79uwXL29TY76Z2rM5mHXA, linux-raid-u79uwXL29TY76Z2rM5mHXA, linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw, Mimi Zohar, Amir Goldstein, linux-kernel-u79uwXL29TY76Z2rM5mHXA, dhowells-H+wXaHxf7aLQT0dZR+AlfA, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA, linux-api-u79uwXL29TY76Z2rM5mHXA, Joe Perches, Andy Shevchenko, Shaohua Li, Steven Whitehouse Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org> 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <13041.1495191521-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>]
* Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header [not found] ` <13041.1495191521-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org> @ 2017-05-21 6:55 ` Christoph Hellwig 0 siblings, 0 replies; 2+ messages in thread From: Christoph Hellwig @ 2017-05-21 6:55 UTC (permalink / raw) To: David Howells Cc: linux-raid-u79uwXL29TY76Z2rM5mHXA, linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw, Mimi Zohar, Amir Goldstein, linux-kernel-u79uwXL29TY76Z2rM5mHXA, Steven Whitehouse, linux-xfs-u79uwXL29TY76Z2rM5mHXA, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA, linux-api-u79uwXL29TY76Z2rM5mHXA, Joe Perches, Andy Shevchenko, Shaohua Li, Christoph Hellwig On Fri, May 19, 2017 at 11:58:41AM +0100, David Howells wrote: > Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org> 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. It is never passed through any kernel interface, which by defintion does not make it an ABI. And even if it was we are not going to change the ABI for a uuid_t ever. We're just changing the internal name, and stop exposing the old name which was never used in an ABI to userspace. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-21 6:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20170518071352.GA515@lst.de>
[not found] ` <20170518062705.25902-1-hch@lst.de>
[not found] ` <20170518062705.25902-4-hch@lst.de>
[not found] ` <1495091565.31562.28.camel@perches.com>
[not found] ` <20170518071352.GA515-jcswGhMUV9g@public.gmane.org>
2017-05-19 10:58 ` [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header David Howells
[not found] ` <13041.1495191521-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2017-05-21 6:55 ` Christoph Hellwig
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).