linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
To: "Colin King" <colin.king@canonical.com>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"David Zhou" <David1.Zhou@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] drm/amd/display: fix spelling mistake "exeuction" -> "execution"
Date: Mon, 11 Nov 2019 08:37:31 -0500	[thread overview]
Message-ID: <633bbabf-56d4-ad4a-9d4e-9562e7122d17@amd.com> (raw)
In-Reply-To: <20191109194923.231655-1-colin.king@canonical.com>

On 2019-11-09 2:49 p.m., Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> There are spelling mistakes in a DC_ERROR message and a comment.
> Fix these.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>

Thanks!

Nicholas Kazlauskas

> ---
>   drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c    | 2 +-
>   drivers/gpu/drm/amd/display/dmub/inc/dmub_srv.h | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c b/drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c
> index 61cefe0a3790..b65b66025267 100644
> --- a/drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c
> +++ b/drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c
> @@ -92,7 +92,7 @@ void dc_dmub_srv_cmd_execute(struct dc_dmub_srv *dc_dmub_srv)
>   
>   	status = dmub_srv_cmd_execute(dmub);
>   	if (status != DMUB_STATUS_OK)
> -		DC_ERROR("Error starting DMUB exeuction: status=%d\n", status);
> +		DC_ERROR("Error starting DMUB execution: status=%d\n", status);
>   }
>   
>   void dc_dmub_srv_wait_idle(struct dc_dmub_srv *dc_dmub_srv)
> diff --git a/drivers/gpu/drm/amd/display/dmub/inc/dmub_srv.h b/drivers/gpu/drm/amd/display/dmub/inc/dmub_srv.h
> index aa8f0396616d..45e427d1952e 100644
> --- a/drivers/gpu/drm/amd/display/dmub/inc/dmub_srv.h
> +++ b/drivers/gpu/drm/amd/display/dmub/inc/dmub_srv.h
> @@ -416,7 +416,7 @@ enum dmub_status dmub_srv_cmd_queue(struct dmub_srv *dmub,
>    * dmub_srv_cmd_execute() - Executes a queued sequence to the dmub
>    * @dmub: the dmub service
>    *
> - * Begins exeuction of queued commands on the dmub.
> + * Begins execution of queued commands on the dmub.
>    *
>    * Return:
>    *   DMUB_STATUS_OK - success
> 


  reply	other threads:[~2019-11-11 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09 19:49 [PATCH][next] drm/amd/display: fix spelling mistake "exeuction" -> "execution" Colin King
2019-11-11 13:37 ` Kazlauskas, Nicholas [this message]
2019-11-11 17:28   ` 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=633bbabf-56d4-ad4a-9d4e-9562e7122d17@amd.com \
    --to=nicholas.kazlauskas@amd.com \
    --cc=David1.Zhou@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=colin.king@canonical.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunpeng.li@amd.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;
as well as URLs for NNTP newsgroup(s).