From: "Christian König" <christian.koenig@amd.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
alexander.deucher@amd.com, airlied@linux.ie, daniel@ffwll.ch,
jdelvare@suse.de, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH] drivers: amdgpu: amdgpu_display: Fixed the spelling of falg to flag
Date: Tue, 10 Nov 2020 12:56:09 +0100 [thread overview]
Message-ID: <6eaddf7a-7fc8-ea2a-41f8-d5e66b9ea28a@amd.com> (raw)
In-Reply-To: <20201109210725.24668-1-unixbhaskar@gmail.com>
Am 09.11.20 um 22:07 schrieb Bhaskar Chowdhury:
> s/falg/flag/p
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_display.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_display.c
> index 2e8a8b57639f..9223502c1e5b 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_display.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_display.c
> @@ -509,7 +509,7 @@ uint32_t amdgpu_display_supported_domains(struct amdgpu_device *adev,
> * to avoid hang caused by placement of scanout BO in GTT on certain
> * APUs. So force the BO placement to VRAM in case this architecture
> * will not allow USWC mappings.
> - * Also, don't allow GTT domain if the BO doens't have USWC falg set.
> + * Also, don't allow GTT domain if the BO doens't have USWC flag set.
> */
> if ((bo_flags & AMDGPU_GEM_CREATE_CPU_GTT_USWC) &&
> amdgpu_bo_support_uswc(bo_flags) &&
> --
> 2.26.2
>
prev parent reply other threads:[~2020-11-10 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 21:07 Bhaskar Chowdhury
2020-11-09 21:21 ` Alex Deucher
2020-11-10 11:56 ` Christian König [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=6eaddf7a-7fc8-ea2a-41f8-d5e66b9ea28a@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jdelvare@suse.de \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=unixbhaskar@gmail.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
Powered by JetHome