From: Frank Binns <Frank.Binns@imgtec.com>
To: "tzimmermann@suse.de" <tzimmermann@suse.de>,
Donald Robson <Donald.Robson@imgtec.com>,
Matt Coster <Matt.Coster@imgtec.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"colin.i.king@gmail.com" <colin.i.king@gmail.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"mripard@kernel.org" <mripard@kernel.org>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] drm/imagination: Fix a couple of spelling mistakes in literal strings
Date: Mon, 27 Nov 2023 10:40:22 +0000 [thread overview]
Message-ID: <e0575791d72a69fec7100d17a9232641f7a4c836.camel@imgtec.com> (raw)
In-Reply-To: <20231124163917.300685-1-colin.i.king@gmail.com>
Hi Colin,
Thank you for the patch.
On Fri, 2023-11-24 at 16:39 +0000, Colin Ian King wrote:
> There are a couple of spelling mistakes in literal strings in the
> stid_fmts array. Fix these.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Frank Binns <frank.binns@imgtec.com>
> ---
> drivers/gpu/drm/imagination/pvr_rogue_fwif_sf.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_rogue_fwif_sf.h b/drivers/gpu/drm/imagination/pvr_rogue_fwif_sf.h
> index 571954182f33..56e11009e123 100644
> --- a/drivers/gpu/drm/imagination/pvr_rogue_fwif_sf.h
> +++ b/drivers/gpu/drm/imagination/pvr_rogue_fwif_sf.h
> @@ -497,7 +497,7 @@ static const struct rogue_km_stid_fmt stid_fmts[] = {
> { ROGUE_FW_LOG_CREATESFID(213, ROGUE_FW_GROUP_MAIN, 1),
> "Safety Watchdog threshold period set to 0x%x clock cycles" },
> { ROGUE_FW_LOG_CREATESFID(214, ROGUE_FW_GROUP_MAIN, 0),
> - "MTS Safety Event trigged by the safety watchdog." },
> + "MTS Safety Event triggered by the safety watchdog." },
> { ROGUE_FW_LOG_CREATESFID(215, ROGUE_FW_GROUP_MAIN, 3),
> "DM%d USC tasks range limit 0 - %d, stride %d" },
> { ROGUE_FW_LOG_CREATESFID(216, ROGUE_FW_GROUP_MAIN, 1),
> @@ -1114,7 +1114,7 @@ static const struct rogue_km_stid_fmt stid_fmts[] = {
> { ROGUE_FW_LOG_CREATESFID(39, ROGUE_FW_GROUP_SPM, 2),
> "3DMemFree matches freelist 0x%08x (FL type = %u)" },
> { ROGUE_FW_LOG_CREATESFID(40, ROGUE_FW_GROUP_SPM, 0),
> - "Raise the 3DMemFreeDedected flag" },
> + "Raise the 3DMemFreeDetected flag" },
> { ROGUE_FW_LOG_CREATESFID(41, ROGUE_FW_GROUP_SPM, 1),
> "Wait for pending grow on Freelist 0x%08x" },
> { ROGUE_FW_LOG_CREATESFID(42, ROGUE_FW_GROUP_SPM, 1),
next prev parent reply other threads:[~2023-11-27 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 16:39 Colin Ian King
2023-11-27 10:40 ` Frank Binns [this message]
2023-11-28 13:00 ` (subset) " Maxime Ripard
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=e0575791d72a69fec7100d17a9232641f7a4c836.camel@imgtec.com \
--to=frank.binns@imgtec.com \
--cc=Donald.Robson@imgtec.com \
--cc=Matt.Coster@imgtec.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=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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
all inboxes | Powered by JetHome®