From: Alain Volmat <alain.volmat@foss.st.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: 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/sti: Fix spelling mistake "top_cmd_offest" -> "top_cmd_offset"
Date: Mon, 13 Feb 2023 19:06:08 +0100 [thread overview]
Message-ID: <20230213180608.GA1925841@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <20230213100522.106595-1-colin.i.king@gmail.com>
Hi,
thanks for the patch.
On Mon, Feb 13, 2023 at 10:05:22AM +0000, Colin Ian King wrote:
> There is a spelling mistake in a variable name. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/gpu/drm/sti/sti_hqvdp.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/sti/sti_hqvdp.c b/drivers/gpu/drm/sti/sti_hqvdp.c
> index 02b77279f6e4..711a6e333afc 100644
> --- a/drivers/gpu/drm/sti/sti_hqvdp.c
> +++ b/drivers/gpu/drm/sti/sti_hqvdp.c
> @@ -797,7 +797,7 @@ static void sti_hqvdp_disable(struct sti_hqvdp *hqvdp)
> static int sti_hqvdp_vtg_cb(struct notifier_block *nb, unsigned long evt, void *data)
> {
> struct sti_hqvdp *hqvdp = container_of(nb, struct sti_hqvdp, vtg_nb);
> - int btm_cmd_offset, top_cmd_offest;
> + int btm_cmd_offset, top_cmd_offset;
> struct sti_hqvdp_cmd *btm_cmd, *top_cmd;
>
> if ((evt != VTG_TOP_FIELD_EVENT) && (evt != VTG_BOTTOM_FIELD_EVENT)) {
> @@ -816,14 +816,14 @@ static int sti_hqvdp_vtg_cb(struct notifier_block *nb, unsigned long evt, void *
> if (hqvdp->btm_field_pending) {
> /* Create the btm field command from the current one */
> btm_cmd_offset = sti_hqvdp_get_free_cmd(hqvdp);
> - top_cmd_offest = sti_hqvdp_get_curr_cmd(hqvdp);
> - if ((btm_cmd_offset == -1) || (top_cmd_offest == -1)) {
> + top_cmd_offset = sti_hqvdp_get_curr_cmd(hqvdp);
> + if ((btm_cmd_offset == -1) || (top_cmd_offset == -1)) {
> DRM_DEBUG_DRIVER("Warning: no cmd, will skip field\n");
> return -EBUSY;
> }
>
> btm_cmd = hqvdp->hqvdp_cmd + btm_cmd_offset;
> - top_cmd = hqvdp->hqvdp_cmd + top_cmd_offest;
> + top_cmd = hqvdp->hqvdp_cmd + top_cmd_offset;
>
> memcpy(btm_cmd, top_cmd, sizeof(*btm_cmd));
>
> --
Acked-by: Alain Volmat <alain.volmat@foss.st.com>
Alain
> 2.30.2
>
prev parent reply other threads:[~2023-02-13 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 10:05 Colin Ian King
2023-02-13 18:06 ` Alain Volmat [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=20230213180608.GA1925841@gnbcxd0016.gnb.st.com \
--to=alain.volmat@foss.st.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 \
/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®