Skip to contentSkip to conversation

driver core: fix path of /sys/module in comment

PATCH Applied Zenghui Yu 3 participants 3 messages Jun 21 – Jun 28 Driver core

lore
Share & tools
lore

Zenghui Yu

author
#0 lore raw

PATCH 1/1 driver core: fix path of /sys/module in comment

The comment wrongly references to /sys/modules directory instead of /sys/module. Fix it.

---
 drivers/base/module.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/base/module.c +1 -1
index 218aaa096455..6789dca485ab 100644
@@ -42,7 +42,7 @@ int module_add_driver(struct module *mod, const struct device_driver *drv)
 	if (mod)
 		mk = &mod->mkobj;
 	else if (drv->mod_name) {
-		/* Lookup or create built-in module entry in /sys/modules */
+		/* Lookup or create built-in module entry in /sys/module */
 		mk = lookup_or_create_module_kobject(drv->mod_name);
 		if (mk) {
 			/* remember our module structure */
Signature · 1 line
2.53.0
Acked-by on v1 1/1
#1 lore raw
Quoted 4 lines · Zenghui Yu

The comment wrongly references to /sys/modules directory instead of /sys/module. Fix it.

Thanks.

Quoted 17 lines
---
 drivers/base/module.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/base/module.c +1 -1
index 218aaa096455..6789dca485ab 100644
@@ -42,7 +42,7 @@ int module_add_driver(struct module *mod, const struct device_driver *drv)
 	if (mod)
 		mk = &mod->mkobj;
 	else if (drv->mod_name) {
-		/* Lookup or create built-in module entry in /sys/modules */
+		/* Lookup or create built-in module entry in /sys/module */
 		mk = lookup_or_create_module_kobject(drv->mod_name);
 		if (mk) {
 			/* remember our module structure */
Signature · 1 line
~Randy
maintainer Applied
#2 lore raw
In reply to Zenghui Yu
Quoted 1 line · Zenghui Yu

[PATCH] driver core: fix path of /sys/module in comment

Applied, thanks!

Branch: driver-core-testing
Tree: git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git

[1/1] driver core: fix path of /sys/module in comment

      commit: e7e09a8546a9

The patch will appear in the next linux-next integration (typically within 24 hours on weekdays).

The patch is in the driver-core-testing branch and will be promoted to driver-core-next after validation.