From: "Christian König" <christian.koenig@amd.com>
To: Colin King <colin.king@canonical.com>,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@linux.ie>,
Chunming Zhou <David1.Zhou@amd.com>,
Jerry.Zhang@amd.com,
"Edward O'Callaghan" <funfunctor@folklore1984.net>,
Alex Xie <AlexBin.Xie@amd.com>,
Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: fix spelling mistake: "suuport"-> "support"
Date: Tue, 25 Jul 2017 10:40:41 +0200 [thread overview]
Message-ID: <98e76c8e-fb6e-9ee4-8188-2e290d88e653@amd.com> (raw)
In-Reply-To: <20170724224501.17037-1-colin.king@canonical.com>
Am 25.07.2017 um 00:45 schrieb Colin King:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in WARN_ONCE message
>
> Signed-off-by: Colin Ian King <colin.king@canoical.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 5795f81369f0..06f11e2a32af 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -1301,7 +1301,7 @@ static int amdgpu_vm_update_ptes(struct amdgpu_pte_update_params *params,
>
> if (params->shadow) {
> if (WARN_ONCE(use_cpu_update,
> - "CPU VM update doesn't suuport shadow pages"))
> + "CPU VM update doesn't support shadow pages"))
> return 0;
>
> if (!pt->shadow)
next prev parent reply other threads:[~2017-07-25 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 22:45 Colin King
2017-07-25 8:40 ` Christian König [this message]
2017-07-25 15:45 ` Alex Deucher
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=98e76c8e-fb6e-9ee4-8188-2e290d88e653@amd.com \
--to=christian.koenig@amd.com \
--cc=AlexBin.Xie@amd.com \
--cc=David1.Zhou@amd.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=Jerry.Zhang@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=colin.king@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=funfunctor@folklore1984.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®