[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1698661274-32540-1-git-send-email-quic_mojha@quicinc.com>
Date: Mon, 30 Oct 2023 15:51:14 +0530
From: Mukesh Ojha <quic_mojha@...cinc.com>
To: <gregkh@...uxfoundation.org>, <rafael@...nel.org>
CC: <linux-kernel@...r.kernel.org>,
Mukesh Ojha <quic_mojha@...cinc.com>
Subject: [PATCH] fs/sysfs/dir.c : Fix typo in comment
Typo correction
kboject => kobject
Signed-off-by: Mukesh Ojha <quic_mojha@...cinc.com>
---
fs/sysfs/dir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/sysfs/dir.c b/fs/sysfs/dir.c
index b6b6796e1616..4df2afa551dc 100644
--- a/fs/sysfs/dir.c
+++ b/fs/sysfs/dir.c
@@ -81,7 +81,7 @@ void sysfs_remove_dir(struct kobject *kobj)
struct kernfs_node *kn = kobj->sd;
/*
- * In general, kboject owner is responsible for ensuring removal
+ * In general, kobject owner is responsible for ensuring removal
* doesn't race with other operations and sysfs doesn't provide any
* protection; however, when @kobj is used as a symlink target, the
* symlinking entity usually doesn't own @kobj and thus has no
--
2.7.4
Powered by blists - more mailing lists