From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751412AbdFEOGv (ORCPT ); Mon, 5 Jun 2017 10:06:51 -0400 Received: from mga07.intel.com ([134.134.136.100]:30026 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751318AbdFEOGu (ORCPT ); Mon, 5 Jun 2017 10:06:50 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,300,1493708400"; d="scan'208";a="1156729226" Message-ID: <1496671605.22624.2.camel@linux.intel.com> Subject: Re: new tree for linux-next: uuid From: Andy Shevchenko To: Christoph Hellwig , Stephen Rothwell Cc: Linus Torvalds , linux-kernel@vger.kernel.org Date: Mon, 05 Jun 2017 17:06:45 +0300 In-Reply-To: <20170605080713.GA22028@lst.de> References: <20170604201413.GA12748@lst.de> <20170605094956.069d5af3@canb.auug.org.au> <20170605080713.GA22028@lst.de> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2017-06-05 at 10:07 +0200, Christoph Hellwig wrote: > Meh, thanks.  This has been throught the buildbot countless times > without a report.  But I guess a less generic name might be a good > idea to start with. > > Andy: do you think UUID_INIT/GUID_INIT make sense to your? > or _INITIALIZER? I'm a bit out of context. Where this will be used? P.S. W/o context latter sounds better to me, but... see above. -- Andy Shevchenko Intel Finland Oy