All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Gavin Wan <Gavin.Wan@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amd/amdgpu: Remove static from variable in RLCG Reg RW.
Date: Thu, 14 Apr 2022 19:58:52 +0200	[thread overview]
Message-ID: <9d77bd3d-782b-7866-7ae2-c2f88f1e1002@molgen.mpg.de> (raw)
In-Reply-To: <20220413152641.830023-1-Gavin.Wan@amd.com>

Dear Gavin,


Thank you for your patch.

Am 13.04.22 um 17:26 schrieb Gavin Wan:

Should you re-roll your patch (v2), please remove the dot/period from 
the end of the git commit message summary (subject).

> [why] These static variables saves the RLC Scratch registers address.

s/saves/save/

>        When we installed multiple GPUs (for example: XGMI setting) and

s/installed/install/

>        multiple GPUs call the function at same time. The RLC Scratch

… same time, the RLC …

>        registers address are changed each other. Then it caused

s/caused/causes/

>        reading/writing to wrong GPU.

I see from other patches posted here, that [why] is put on a separate 
line, so you do not need to indent the text.

[why]

These static …

> 
> [fix] Removed the static from the variables. The variables are
>        in stack.

Same here, though *how* instead of *fix* seems more common.

s/Removed/Remove/
s/in stack/on the stack/

> 
> Signed-off-by: Gavin Wan <Gavin.Wan@amd.com>
> Change-Id: Iee78849291d4f7a9688ecc5165bec70ee85cdfbe

Without the Gerrit URL that line is useless.


Kind regards.

Paul


> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
> index d5eea031c3e3..d18a05a20566 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
> @@ -868,11 +868,11 @@ static u32 amdgpu_virt_rlcg_reg_rw(struct amdgpu_device *adev, u32 offset, u32 v
>   	uint32_t timeout = 50000;
>   	uint32_t i, tmp;
>   	uint32_t ret = 0;
> -	static void *scratch_reg0;
> -	static void *scratch_reg1;
> -	static void *scratch_reg2;
> -	static void *scratch_reg3;
> -	static void *spare_int;
> +	void *scratch_reg0;
> +	void *scratch_reg1;
> +	void *scratch_reg2;
> +	void *scratch_reg3;
> +	void *spare_int;
>   
>   	if (!adev->gfx.rlc.rlcg_reg_access_supported) {
>   		dev_err(adev->dev,

  parent reply	other threads:[~2022-04-14 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 15:26 [PATCH] drm/amd/amdgpu: Remove static from variable in RLCG Reg RW Gavin Wan
2022-04-14 14:24 ` Alex Deucher
2022-04-14 17:58 ` Paul Menzel [this message]
2022-04-14 18:34   ` Wan, Gavin

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=9d77bd3d-782b-7866-7ae2-c2f88f1e1002@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=Gavin.Wan@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.