mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"colin.king@canonical.com" <colin.king@canonical.com>,
	Deepak Singh Rawat <drawat@vmware.com>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"airlied@linux.ie" <airlied@linux.ie>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH][drm-next] drm/selftest: fix spelling mistake "dimention" -> "dimenstion"
Date: Mon, 10 Dec 2018 12:50:29 +0000	[thread overview]
Message-ID: <1a41c8390de02ae0e7ca97fb3af033ee522e62fa.camel@vmware.com> (raw)
In-Reply-To: <20181210092619.4016-1-colin.king@canonical.com>

On Mon, 2018-12-10 at 09:26 +0000, Colin King wrote:

Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>

I'll take this in the next pull request unless I'm told otherwise.

/Thomas

> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a spelling mistake in a pr_err message, fix this.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/gpu/drm/selftests/test-drm_damage_helper.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/selftests/test-drm_damage_helper.c
> b/drivers/gpu/drm/selftests/test-drm_damage_helper.c
> index a2f753205a3e..9d2bcdf8bc29 100644
> --- a/drivers/gpu/drm/selftests/test-drm_damage_helper.c
> +++ b/drivers/gpu/drm/selftests/test-drm_damage_helper.c
> @@ -53,7 +53,7 @@ static bool check_damage_clip(struct
> drm_plane_state *state, struct drm_rect *r,
>  	int src_y2 = (state->src.y2 >> 16) + !!(state->src.y2 &
> 0xFFFF);
>  
>  	if (x1 >= x2 || y1 >= y2) {
> -		pr_err("Cannot have damage clip with no dimention.\n");
> +		pr_err("Cannot have damage clip with no dimension.\n");
>  		return false;
>  	}
>  

      parent reply	other threads:[~2018-12-10 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10  9:26 Colin King
2018-12-10  9:30 ` Colin Ian King
2018-12-10 12:50 ` Thomas Hellstrom [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=1a41c8390de02ae0e7ca97fb3af033ee522e62fa.camel@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=airlied@linux.ie \
    --cc=colin.king@canonical.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=drawat@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --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

Powered by JetHome