From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
<intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] drm/i915/selftest: Fix spelling mistake "ofset" -> "offset"
Date: Mon, 3 Feb 2025 16:54:24 -0500 [thread overview]
Message-ID: <Z6E7EDj67tPMSLp9@intel.com> (raw)
In-Reply-To: <20250202221431.199802-1-colin.i.king@gmail.com>
On Sun, Feb 02, 2025 at 10:14:31PM +0000, Colin Ian King wrote:
> There is a spelling mistake in an error message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c
> index 5c397a2df70e..3eff0894c26c 100644
> --- a/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c
> +++ b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c
> @@ -964,7 +964,7 @@ static int __shrink_hole(struct i915_address_space *vm,
> break;
>
> if (igt_timeout(end_time,
> - "%s timed out at ofset %llx [%llx - %llx]\n",
> + "%s timed out at offset %llx [%llx - %llx]\n",
Thanks for your patch, but this has already been fixed
by accc7f5bf230 ("drm/i915/selftests: fix typos in i915/selftests files")
which is already merged to drm-intel-next.
> __func__, addr, hole_start, hole_end)) {
> err = -EINTR;
> break;
> --
> 2.47.2
>
prev parent reply other threads:[~2025-02-03 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 22:14 [PATCH][next] drm/i915/selftest: Fix spelling mistake "ofset" -> "offset" Colin Ian King
2025-02-02 23:00 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2025-02-02 23:17 ` ✗ i915.CI.BAT: failure " Patchwork
2025-02-03 21:54 ` Rodrigo Vivi [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=Z6E7EDj67tPMSLp9@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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.