From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1CC70C74A5B for ; Fri, 17 Mar 2023 14:12:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229894AbjCQOMm (ORCPT ); Fri, 17 Mar 2023 10:12:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229887AbjCQOMk (ORCPT ); Fri, 17 Mar 2023 10:12:40 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8C3412ED7D for ; Fri, 17 Mar 2023 07:12:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1679062359; x=1710598359; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=eifpQLMvSzmeClZNBGX6vEj8f3i9hiF71k3b+Ift7KM=; b=M0ll5rq2ls+zV773rVCY/g2UKA9SeYTo7DJIcUT0JBNQiUifpSS+omF6 w7OTOCl55OQsb5P+zuXEur1biE3fh2hOvkQhKhpHJOzm8kL1BKPWs71ir CS8D4TmxaSOEWpXSA//g0sS8mStW3Sp143sthjs7mdMxlwk/4+QxXGbl5 TKYAFJCG9mr9WlHE4F6zHEuqgWmLBlYK37prIcTw2NmXKDgUz3TrYVdkH 2Z4KOg2eoSScLnuH7fSstpYUJZaAslbUIZ/Zzrs64kvXbf/mqcg3RVDpx +SVhASm2uBzSX53luGCRja/1cWFvZS8rFkoNdT+p/cLUDs8Rn6Edhc67B A==; X-IronPort-AV: E=McAfee;i="6600,9927,10652"; a="326627272" X-IronPort-AV: E=Sophos;i="5.98,268,1673942400"; d="scan'208";a="326627272" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Mar 2023 07:12:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10652"; a="673563000" X-IronPort-AV: E=Sophos;i="5.98,268,1673942400"; d="scan'208";a="673563000" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga007.jf.intel.com with ESMTP; 17 Mar 2023 07:12:15 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pdAoY-0054Uk-0Q; Fri, 17 Mar 2023 16:12:14 +0200 Date: Fri, 17 Mar 2023 16:12:13 +0200 From: Andy Shevchenko To: Greg Kroah-Hartman Cc: Daniele Ceraolo Spurio , Alexander Usyskin , Vitaly Lubart , Tomas Winkler , Alexander Graf , linux-kernel@vger.kernel.org, Arnd Bergmann Subject: Re: [PATCH v1 1/1] mei: Move uuid.h to the MEI namespace Message-ID: References: <20230310170747.22782-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 17, 2023 at 03:07:45PM +0100, Greg Kroah-Hartman wrote: > On Fri, Mar 10, 2023 at 07:07:47PM +0200, Andy Shevchenko wrote: > > There is only a single user of the UUID uAPI, let's make it > > part of that user. > > > > The way it's done is to prevent compilation time breakage for > > the user space that does > > > > #include > > > > In the future MEI user space tools can switch over to use mei_uuid.h. > > When will that happen? I don't know > And why the churn, what's the problem with keeping this as uuid.h? The problem here is a possible confusion with uAPI and internal headers with the same name. -- With Best Regards, Andy Shevchenko