From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Oded Gabbay <ogabbay@kernel.org>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] accel/ivpu: Fix spelling mistake "tansition" -> "transition"
Date: Fri, 20 Jan 2023 10:54:54 +0100 [thread overview]
Message-ID: <20230120095454.GA56856@linux.intel.com> (raw)
In-Reply-To: <20230120092842.79238-1-colin.i.king@gmail.com>
On Fri, Jan 20, 2023 at 09:28:42AM +0000, Colin Ian King wrote:
> There are spelling mistakes in two ivpu_err error messages. Fix them.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> ---
> drivers/accel/ivpu/ivpu_hw_mtl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/accel/ivpu/ivpu_hw_mtl.c b/drivers/accel/ivpu/ivpu_hw_mtl.c
> index b59b1f472b40..62bfaa9081c4 100644
> --- a/drivers/accel/ivpu/ivpu_hw_mtl.c
> +++ b/drivers/accel/ivpu/ivpu_hw_mtl.c
> @@ -608,7 +608,7 @@ static int ivpu_boot_d0i3_drive(struct ivpu_device *vdev, bool enable)
>
> ret = REGB_POLL_FLD(MTL_BUTTRESS_VPU_D0I3_CONTROL, INPROGRESS, 0, TIMEOUT_US);
> if (ret) {
> - ivpu_err(vdev, "Failed to sync before D0i3 tansition: %d\n", ret);
> + ivpu_err(vdev, "Failed to sync before D0i3 transition: %d\n", ret);
> return ret;
> }
>
> @@ -621,7 +621,7 @@ static int ivpu_boot_d0i3_drive(struct ivpu_device *vdev, bool enable)
>
> ret = REGB_POLL_FLD(MTL_BUTTRESS_VPU_D0I3_CONTROL, INPROGRESS, 0, TIMEOUT_US);
> if (ret)
> - ivpu_err(vdev, "Failed to sync after D0i3 tansition: %d\n", ret);
> + ivpu_err(vdev, "Failed to sync after D0i3 transition: %d\n", ret);
>
> return ret;
> }
> --
> 2.30.2
>
WARNING: multiple messages have this Message-ID (diff)
From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Oded Gabbay <ogabbay@kernel.org>,
kernel-janitors@vger.kernel.org,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] accel/ivpu: Fix spelling mistake "tansition" -> "transition"
Date: Fri, 20 Jan 2023 10:54:54 +0100 [thread overview]
Message-ID: <20230120095454.GA56856@linux.intel.com> (raw)
In-Reply-To: <20230120092842.79238-1-colin.i.king@gmail.com>
On Fri, Jan 20, 2023 at 09:28:42AM +0000, Colin Ian King wrote:
> There are spelling mistakes in two ivpu_err error messages. Fix them.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> ---
> drivers/accel/ivpu/ivpu_hw_mtl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/accel/ivpu/ivpu_hw_mtl.c b/drivers/accel/ivpu/ivpu_hw_mtl.c
> index b59b1f472b40..62bfaa9081c4 100644
> --- a/drivers/accel/ivpu/ivpu_hw_mtl.c
> +++ b/drivers/accel/ivpu/ivpu_hw_mtl.c
> @@ -608,7 +608,7 @@ static int ivpu_boot_d0i3_drive(struct ivpu_device *vdev, bool enable)
>
> ret = REGB_POLL_FLD(MTL_BUTTRESS_VPU_D0I3_CONTROL, INPROGRESS, 0, TIMEOUT_US);
> if (ret) {
> - ivpu_err(vdev, "Failed to sync before D0i3 tansition: %d\n", ret);
> + ivpu_err(vdev, "Failed to sync before D0i3 transition: %d\n", ret);
> return ret;
> }
>
> @@ -621,7 +621,7 @@ static int ivpu_boot_d0i3_drive(struct ivpu_device *vdev, bool enable)
>
> ret = REGB_POLL_FLD(MTL_BUTTRESS_VPU_D0I3_CONTROL, INPROGRESS, 0, TIMEOUT_US);
> if (ret)
> - ivpu_err(vdev, "Failed to sync after D0i3 tansition: %d\n", ret);
> + ivpu_err(vdev, "Failed to sync after D0i3 transition: %d\n", ret);
>
> return ret;
> }
> --
> 2.30.2
>
next prev parent reply other threads:[~2023-01-20 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 9:28 [PATCH][next] accel/ivpu: Fix spelling mistake "tansition" -> "transition" Colin Ian King
2023-01-20 9:54 ` Stanislaw Gruszka [this message]
2023-01-20 9:54 ` Stanislaw Gruszka
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=20230120095454.GA56856@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.