From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754645AbdESK6t (ORCPT ); Fri, 19 May 2017 06:58:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52102 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750970AbdESK6p (ORCPT ); Fri, 19 May 2017 06:58:45 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 21DD7734 Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dhowells@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 21DD7734 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20170518071352.GA515@lst.de> References: <20170518071352.GA515@lst.de> <20170518062705.25902-1-hch@lst.de> <20170518062705.25902-4-hch@lst.de> <1495091565.31562.28.camel@perches.com> To: Christoph Hellwig Cc: dhowells@redhat.com, Joe Perches , Andy Shevchenko , Amir Goldstein , linux-fsdevel@vger.kernel.org, Shaohua Li , Dan Williams , Steven Whitehouse , Mimi Zohar , linux-xfs@vger.kernel.org, linux-raid@vger.kernel.org, linux-nvdimm@ml01.01.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13040.1495191521.1@warthog.procyon.org.uk> Date: Fri, 19 May 2017 11:58:41 +0100 Message-ID: <13041.1495191521@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 19 May 2017 10:58:45 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christoph Hellwig 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