[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24291087.1210713535895.JavaMail.oracle@acsmt301.oracle.com>
Date: Tue, 13 May 2008 16:18:55 -0500 (CDT)
From: Randy Dunlap <RANDY.DUNLAP@...CLE.COM>
To: "Eric W. Biederman" <ebiederm@...ssion.com>,
Greg KH <greg@...ah.com>
Cc: Al Viro <viro@....linux.org.uk>,
Benjamin Thery <benjamin.thery@...l.net>,
Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Daniel Lezcano <dlezcano@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Pavel Emelyanov <xemul@...nvz.org>,
"Serge E. Hallyn" <serue@...ibm.com>, Tejun Heo <htejun@...il.com>
Subject: Re: [PATCH] Fix kobject_rename and !CONFIG_SYSFS v3
> Changelog:
> v3: Documentation typo fixes
Inserted/attached wrong patch file?
I don't see any text changes.
> diff --git a/Documentation/kobject.txt b/Documentation/kobject.txt
> index bf3256e..79184b4 100644
> --- a/Documentation/kobject.txt
> +++ b/Documentation/kobject.txt
> @@ -118,6 +118,10 @@ the name of the kobject, call kobject_rename():
>
> int kobject_rename(struct kobject *kobj, const char
> *new_name);
>
> +Note kobject_rename does perform any locking or have a solid
> notion of
> +what names are valid so the provide must provide their own
> sanity checking
> +and serialization.
> +
> There is a function called kobject_set_name() but that is
> legacy cruft and
> is being removed. If your code needs to call this function,
> it is
> incorrect and needs to be fixed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists