public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Huang Ying <ying.huang@intel.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	"Dan Williams" <dan.j.williams@intel.com>,
	Bharata B Rao <bharata@amd.com>,
	Alistair Popple <apopple@nvidia.com>,
	"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>
Subject: Re: [PATCH] acpi,hmat: Use ACCESS_COORDINATE_CPU when appropriate
Date: Thu, 6 Jun 2024 10:03:43 +0100	[thread overview]
Message-ID: <20240606100343.000075ea@Huawei.com> (raw)
In-Reply-To: <20240606022845.189710-1-ying.huang@intel.com>

On Thu,  6 Jun 2024 10:28:45 +0800
Huang Ying <ying.huang@intel.com> wrote:

> To improve the readability of the code via replacing the magic number
> "1" with ACCESS_COORDINATE_CPU when appropriate.  No functionality
> change.
> 
> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Bharata B Rao <bharata@amd.com>
> Cc: Alistair Popple <apopple@nvidia.com>
> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Good to clean this up. Thanks!

Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

> ---
>  drivers/acpi/numa/hmat.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/acpi/numa/hmat.c b/drivers/acpi/numa/hmat.c
> index 2c8ccc91ebe6..febd9e51350b 100644
> --- a/drivers/acpi/numa/hmat.c
> +++ b/drivers/acpi/numa/hmat.c
> @@ -408,7 +408,7 @@ static __init void hmat_update_target(unsigned int tgt_pxm, unsigned int init_px
>  	if (target && target->processor_pxm == init_pxm) {
>  		hmat_update_target_access(target, type, value,
>  					  ACCESS_COORDINATE_LOCAL);
> -		/* If the node has a CPU, update access 1 */
> +		/* If the node has a CPU, update access ACCESS_COORDINATE_CPU */
>  		if (node_state(pxm_to_node(init_pxm), N_CPU))
>  			hmat_update_target_access(target, type, value,
>  						  ACCESS_COORDINATE_CPU);
> @@ -948,7 +948,7 @@ static int hmat_set_default_dram_perf(void)
>  		target = find_mem_target(pxm);
>  		if (!target)
>  			continue;
> -		attrs = &target->coord[1];
> +		attrs = &target->coord[ACCESS_COORDINATE_CPU];
>  		rc = mt_set_default_dram_perf(nid, attrs, "ACPI HMAT");
>  		if (rc)
>  			return rc;
> @@ -975,7 +975,7 @@ static int hmat_calculate_adistance(struct notifier_block *self,
>  	hmat_update_target_attrs(target, p_nodes, ACCESS_COORDINATE_CPU);
>  	mutex_unlock(&target_lock);
>  
> -	perf = &target->coord[1];
> +	perf = &target->coord[ACCESS_COORDINATE_CPU];
>  
>  	if (mt_perf_to_adistance(perf, adist))
>  		return NOTIFY_OK;


  reply	other threads:[~2024-06-06  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  2:28 [PATCH] acpi,hmat: Use ACCESS_COORDINATE_CPU when appropriate Huang Ying
2024-06-06  9:03 ` Jonathan Cameron [this message]
2024-06-06 15:59 ` Dave Jiang

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=20240606100343.000075ea@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=apopple@nvidia.com \
    --cc=bharata@amd.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ying.huang@intel.com \
    /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