From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Subject: Re: [PATCH v1 05/10] ACPI: switch to use generic UUID API Date: Fri, 26 Feb 2016 15:46:31 +0200 Message-ID: <1456494391.13244.137.camel@linux.intel.com> References: <1455711448-124103-1-git-send-email-andriy.shevchenko@linux.intel.com> <1455711448-124103-6-git-send-email-andriy.shevchenko@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Dan Williams Cc: "Rafael J. Wysocki" , Theodore Ts'o , Arnd Bergmann , Greg Kroah-Hartman , Jarkko Sakkinen , Jani Nikula , David Airlie , Benjamin Tissoires , Bjorn Helgaas , Mathias Nyman , Matt Fleming , Lv Zheng , Mark Brown , Zhang Rui , Mika Westerberg , Andrew Morton , Rasmus Villemoes , Linux ACPI , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Maling list - DRI developers , linux-efi-u79uwXL29TbrhsbdSgBK9A@public.gmane.org List-Id: dri-devel@lists.freedesktop.org On Wed, 2016-02-17 at 09:49 -0800, Dan Williams wrote: > On Wed, Feb 17, 2016 at 4:17 AM, Andy Shevchenko > wrote: > > Instead of opencoding the existing library functions let's use them > > directly. > >=20 > > The conversion fixes a potential bug in int340x_thermal as well > > since we have > > to use memcmp() on binary data. [..] > > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0uuid_le_to_bin(UUID_NFIT= _BUS, &nfit_uuid[NFIT_DEV_BUS]); > > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0uuid_le_to_bin(UUID_NFIT= _DIMM, &nfit_uuid[NFIT_DEV_DIMM]); >=20 > I don't see the benefit of this change. The benefit is to have less places (ideally one) which provides UUID helper routines for kernel. > =C2=A0=C2=A0For the NFIT driver we went > through a fire drill trying to make sure the ACPI spec format of a > UUID matched the Linux interpretation, and this change makes that > harder to determine.=C2=A0=C2=A0 How harder? At least you look into one place and see exactly all functions related. Besides this series actually uses the same approach that was used in ACPI. > ACPI drivers should use ACPICA uuid helper > routines in my opinion. As far as I can see ACPICA lacks of needed API. --=20 Andy Shevchenko Intel Finland Oy