From: Boris Brezillon <boris.brezillon@collabora.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Steven Price <steven.price@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] drm/panthor: Fix spelling mistake "readyness" -> "readiness"
Date: Tue, 26 Mar 2024 11:59:34 +0100 [thread overview]
Message-ID: <20240326115934.726d3ca1@collabora.com> (raw)
In-Reply-To: <20240326100219.43989-1-colin.i.king@gmail.com>
On Tue, 26 Mar 2024 10:02:19 +0000
Colin Ian King <colin.i.king@gmail.com> wrote:
> There is a spelling mistake in a drm_err message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Queued to drm-misc-next.
> ---
> drivers/gpu/drm/panthor/panthor_gpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_gpu.c b/drivers/gpu/drm/panthor/panthor_gpu.c
> index 6dbbc4cfbe7e..0f7c962440d3 100644
> --- a/drivers/gpu/drm/panthor/panthor_gpu.c
> +++ b/drivers/gpu/drm/panthor/panthor_gpu.c
> @@ -333,7 +333,7 @@ int panthor_gpu_block_power_on(struct panthor_device *ptdev,
> val, (mask32 & val) == mask32,
> 100, timeout_us);
> if (ret) {
> - drm_err(&ptdev->base, "timeout waiting on %s:%llx readyness",
> + drm_err(&ptdev->base, "timeout waiting on %s:%llx readiness",
> blk_name, mask);
> return ret;
> }
prev parent reply other threads:[~2024-03-26 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 10:02 [PATCH][next] drm/panthor: Fix spelling mistake "readyness" -> "readiness" Colin Ian King
2024-03-26 10:14 ` Liviu Dudau
2024-03-26 10:26 ` Boris Brezillon
2024-03-26 10:59 ` Boris Brezillon [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=20240326115934.726d3ca1@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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