[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <810e5883-609e-1d5f-fb3a-655ba21d9ee0@quicinc.com>
Date: Tue, 5 Dec 2023 17:07:46 +0530
From: Mukesh Ojha <quic_mojha@...cinc.com>
To: <gregkh@...uxfoundation.org>, <rafael@...nel.org>
CC: <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fs/sysfs/dir.c : Fix typo in comment
I know, this is very minor patch., floating this up again to see
incase we want to consider..
-Mukesh
On 10/30/2023 3:51 PM, Mukesh Ojha wrote:
> 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
Powered by blists - more mailing lists