From: Kexin Sun <kexinsun@smail.nju.edu.cn>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: julia.lawall@inria.fr, xutong.ma@inria.fr,
kexinsun@smail.nju.edu.cn, yunbolyu@smu.edu.sg,
ratnadiraw@smu.edu.sg
Subject: [PATCH] drm/sysfs: update outdated comment for renamed drm_sysfs_connector_status_event()
Date: Sat, 21 Mar 2026 18:57:39 +0800 [thread overview]
Message-ID: <20260321105739.6472-1-kexinsun@smail.nju.edu.cn> (raw)
The function drm_sysfs_connector_status_event() was renamed to
drm_sysfs_connector_property_event() by commit 0cf8d292ba5e
("drm/sysfs: rename drm_sysfs_connector_status_event()"). Update
the comment in drm_sysfs_hotplug_event() accordingly, including
changing "connector status change" to "connector property change"
to match the rename rationale.
Assisted-by: unnamed:deepseek-v3.2 coccinelle
Signed-off-by: Kexin Sun <kexinsun@smail.nju.edu.cn>
---
drivers/gpu/drm/drm_sysfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c
index ef4e923a8728..c543249d32c3 100644
--- a/drivers/gpu/drm/drm_sysfs.c
+++ b/drivers/gpu/drm/drm_sysfs.c
@@ -438,8 +438,8 @@ void drm_sysfs_lease_event(struct drm_device *dev)
* set HOTPLUG=1 in the uevent environment, but this could be expanded to
* deal with other types of events.
*
- * Any new uapi should be using the drm_sysfs_connector_status_event()
- * for uevents on connector status change.
+ * Any new uapi should be using the drm_sysfs_connector_property_event()
+ * for uevents on connector property change.
*/
void drm_sysfs_hotplug_event(struct drm_device *dev)
{
--
2.25.1
next reply other threads:[~2026-03-21 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 10:57 Kexin Sun [this message]
2026-03-21 17:06 ` Claude review: drm/sysfs: update outdated comment for renamed drm_sysfs_connector_status_event() Claude Code Review Bot
2026-03-21 17:06 ` Claude Code Review Bot
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=20260321105739.6472-1-kexinsun@smail.nju.edu.cn \
--to=kexinsun@smail.nju.edu.cn \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ratnadiraw@smu.edu.sg \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=xutong.ma@inria.fr \
--cc=yunbolyu@smu.edu.sg \
/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