From: Colin Ian King <colin.i.king@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@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, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] drm/i915/bw: Fix spelling mistake "threshod" -> "threshold"
Date: Mon, 20 Jul 2026 17:16:30 +0100 [thread overview]
Message-ID: <20260720161630.326016-1-colin.i.king@gmail.com> (raw)
There is a spelling mistake in a drm_dbg_kms message. Fix it.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
drivers/gpu/drm/i915/display/intel_bw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
index 546d5ccbe052..c71082852cfa 100644
--- a/drivers/gpu/drm/i915/display/intel_bw.c
+++ b/drivers/gpu/drm/i915/display/intel_bw.c
@@ -625,7 +625,7 @@ static void xe3_add_peakbw_threshold(struct intel_display *display)
for (int i = 0; i < ARRAY_SIZE(display->bw.max); i++)
display->bw.max[i].deratedbw[qgv_points] = PEAK_BW_THRESHOLD;
- drm_dbg_kms(display->drm, "An extra QGV point %d added for Peak bw threshod of %d\n",
+ drm_dbg_kms(display->drm, "An extra QGV point %d added for Peak bw threshold of %d\n",
qgv_points, PEAK_BW_THRESHOLD);
}
--
2.53.0
next reply other threads:[~2026-07-20 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 16:16 Colin Ian King [this message]
2026-07-20 17:29 ` ✓ CI.KUnit: success for drm/i915/bw: Fix spelling mistake "threshod" -> "threshold" Patchwork
2026-07-20 18:37 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-21 1:16 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-07-21 17:28 ` [PATCH][next] " Rodrigo Vivi
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=20260720161630.326016-1-colin.i.king@gmail.com \
--to=colin.i.king@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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=rodrigo.vivi@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox