From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Subject: Re: [PATCH v2 1/3] ACPI / utils: Introduce acpi_dev_get_dev_name() Date: Fri, 05 Jan 2018 14:22:00 +0200 Message-ID: <1515154920.7000.732.camel@linux.intel.com> References: <20180104164709.64387-1-andriy.shevchenko@linux.intel.com> <20180104164709.64387-2-andriy.shevchenko@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com ([192.55.52.93]:62326 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751487AbeAEM0e (ORCPT ); Fri, 5 Jan 2018 07:26:34 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , Erik Schmauss , ACPI Devel Maling List , Pierre-Louis Bossart , Liam Girdwood , Mark Brown , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , Linus Walleij , linux-gpio@vger.kernel.org, Mika Westerberg On Fri, 2018-01-05 at 13:06 +0100, Rafael J. Wysocki wrote: > On Thu, Jan 4, 2018 at 5:47 PM, Andy Shevchenko > wrote: > > Sometimes the user want to have device name of the match rather than > > just checking if device present or not. > > I would give an example here. You mean to mention what is in patch 2? I can do that. "Subset of Intel ASoC drivers is an existing user of this API when they need to find an actual instance of the codec device based on its ACPI HID." > > To make life easier for such > > users introduce acpi_dev_get_dev_name() > > What about acpi_dev_get_match_name() or just acpi_dev_match_name()? It's "get", not "match". So, acpi_dev_get_name() then? -- Andy Shevchenko Intel Finland Oy