From: TAKANO Mitsuhiro <takano32@gmail.com>
To: dri-devel@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: "David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>,
"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Ankit Nautiyal" <ankit.k.nautiyal@intel.com>,
linux-kernel@vger.kernel.org,
"TAKANO Mitsuhiro" <takano32@gmail.com>
Subject: [PATCH] drm/connector: Fix misspellings in the HDMI 2.1 capability comments
Date: Fri, 20 Nov 2026 20:56:40 +0000 [thread overview]
Message-ID: <20261120205640.1466229-1-takano32@gmail.com> (raw)
Three comment lines misspell a word: "fom" for "from" in the kernel-doc of
both struct drm_hdmi_vrr_cap and struct drm_hdmi_dsc_cap, and "inide" for
"inside" in the comment of the vrr_min member.
The two in struct drm_hdmi_vrr_cap came in with 014da1db5e64, the one in
struct drm_hdmi_dsc_cap with 76ee7b905678.
Two members of struct drm_hdmi_vrr_cap are documented under a name with a
leading "m" that the struct does not have, @mcnmvrr for cnmvrr and
@mcinema_vrr for cinema_vrr. A patch for that is on the list already, so
it is left out here, and kernel-doc reports the same warnings with and
without this change.
Written with Hermes Agent, an LLM assistant; the author reviewed it and ran
kernel-doc on the file with and without the change.
Fixes: 014da1db5e64 ("drm/edid: parse HDMI 2.1 gaming (ALLM/VRR) capabilities from HF-VSDB")
Fixes: 76ee7b905678 ("drm/edid: Parse DSC1.2 cap fields from HFVSDB block")
Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
---
include/drm/drm_connector.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
index 2ee7c59329aa..f5bfb0f0e7ed 100644
--- a/include/drm/drm_connector.h
+++ b/include/drm/drm_connector.h
@@ -259,7 +259,7 @@ struct drm_scdc {
* struct drm_hdmi_vrr_cap - Information about VRR capabilities of a HDMI sink
*
* Describes the VRR support provided by HDMI 2.1 sink. The information is
- * fetched fom additional HFVSDB blocks defined for HDMI 2.1.
+ * fetched from additional HFVSDB blocks defined for HDMI 2.1.
*/
struct drm_hdmi_vrr_cap {
/** @fva: flag for Fast VActive (Quick Frame Transport) support */
@@ -276,7 +276,7 @@ struct drm_hdmi_vrr_cap {
/**
* @vrr_min : minimum supported variable refresh rate in Hz.
- * Valid values only inide 1 - 48 range
+ * Valid values only inside 1 - 48 range
*/
u16 vrr_min;
@@ -297,7 +297,7 @@ struct drm_hdmi_vrr_cap {
* struct drm_hdmi_dsc_cap - DSC capabilities of HDMI sink
*
* Describes the DSC support provided by HDMI 2.1 sink.
- * The information is fetched fom additional HFVSDB blocks defined
+ * The information is fetched from additional HFVSDB blocks defined
* for HDMI 2.1.
*/
struct drm_hdmi_dsc_cap {
base-commit: d0f871bfb831705d9f55479f5b2b40f636ea7b16
--
2.53.0
reply other threads:[~2026-11-20 20:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261120205640.1466229-1-takano32@gmail.com \
--to=takano32@gmail.com \
--cc=Jerry.Zuo@amd.com \
--cc=airlied@gmail.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomasz.pakula.oficjalny@gmail.com \
--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®