public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] ACPI: scan: Fix up _DEP-related terminology with supplier/consumer
Date: Mon, 7 Dec 2020 19:21:50 +0100	[thread overview]
Message-ID: <054cc790-bebb-9c84-e14c-16b9460d1636@redhat.com> (raw)
In-Reply-To: <6314382.p3e4rEhblS@kreacher>

Hi,

On 12/7/20 6:46 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> The ACPI namespace scanning code uses the terms master/slave when
> populating the list of _DEP dependencies, but that use has no
> external exposures and is not mandated by nor associated with any
> external specifications.
> 
> Change the language used through-out to supplier/consumer.
> 
> No functional impact.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans



> ---
>  drivers/acpi/scan.c |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> Index: linux-pm/drivers/acpi/scan.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/scan.c
> +++ linux-pm/drivers/acpi/scan.c
> @@ -51,8 +51,8 @@ static u64 spcr_uart_addr;
>  
>  struct acpi_dep_data {
>  	struct list_head node;
> -	acpi_handle master;
> -	acpi_handle slave;
> +	acpi_handle supplier;
> +	acpi_handle consumer;
>  };
>  
>  void acpi_scan_lock_acquire(void)
> @@ -1881,8 +1881,8 @@ static void acpi_device_dep_initialize(s
>  		if (!dep)
>  			return;
>  
> -		dep->master = dep_devices.handles[i];
> -		dep->slave  = adev->handle;
> +		dep->supplier = dep_devices.handles[i];
> +		dep->consumer  = adev->handle;
>  		adev->dep_unmet++;
>  
>  		mutex_lock(&acpi_dep_list_lock);
> @@ -2058,8 +2058,8 @@ void acpi_walk_dep_device_list(acpi_hand
>  
>  	mutex_lock(&acpi_dep_list_lock);
>  	list_for_each_entry_safe(dep, tmp, &acpi_dep_list, node) {
> -		if (dep->master == handle) {
> -			acpi_bus_get_device(dep->slave, &adev);
> +		if (dep->supplier == handle) {
> +			acpi_bus_get_device(dep->consumer, &adev);
>  			if (!adev)
>  				continue;
>  
> 
> 
> 


      reply	other threads:[~2020-12-07 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 17:46 [PATCH] ACPI: scan: Fix up _DEP-related terminology with supplier/consumer Rafael J. Wysocki
2020-12-07 18:21 ` Hans de Goede [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=054cc790-bebb-9c84-e14c-16b9460d1636@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox