From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:49827 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755173AbdEDN7Q (ORCPT ); Thu, 4 May 2017 09:59:16 -0400 Date: Thu, 4 May 2017 15:59:13 +0200 From: Christoph Hellwig To: Amir Goldstein Cc: Christoph Hellwig , "Darrick J . Wong" , Miklos Szeredi , Theodore Tso , Richard Weinberger , Mark Fasheh , Dan Williams , Andy Shevchenko , David Howells , Shaohua Li , Al Viro , linux-xfs , linux-unionfs@vger.kernel.org, linux-fsdevel Subject: Re: [PATCH v2 2/8] xfs: re-define uuid_t as common struct uuid_v1 Message-ID: <20170504135913.GA17831@lst.de> References: <1493904383-2187-1-git-send-email-amir73il@gmail.com> <1493904383-2187-3-git-send-email-amir73il@gmail.com> <20170504133417.GD17222@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, May 04, 2017 at 04:57:51PM +0300, Amir Goldstein wrote: > I did consider defining uuid_t as uuid_be. > most of the patch set would have remained the same and > xfs_uuid_getnodeuniq() would use struct uuid_v1 explicitly > instead of implicitly. At least don't add new users of uuid_v1. Moving that stuff into uuid.[ch] was a major mistake, and I wish review would have caught it back then.