X-Git-Url: http://ftp.safe.ca/?a=blobdiff_plain;f=Documentation%2Fkobject.txt;h=b2e374586bd8627719167011a992ec3eb81a1c96;hb=21515e46bc6a6279dd13f6c01898ada9720100a3;hp=bf3256e04027686430823fe32333fabf968a3de4;hpb=36d78d6c5b50ba945bbdee9bf1d8daac00154e02;p=safe%2Fjmp%2Flinux-2.6

diff --git a/Documentation/kobject.txt b/Documentation/kobject.txt
index bf3256e..b2e3745 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);
 
+kobject_rename does not perform any locking or have a solid notion of
+what names are valid so the caller 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.
@@ -305,7 +309,7 @@ should not be manipulated by any other user.
 
 A kset keeps its children in a standard kernel linked list.  Kobjects point
 back to their containing kset via their kset field. In almost all cases,
-the kobjects belonging to a ket have that kset (or, strictly, its embedded
+the kobjects belonging to a kset have that kset (or, strictly, its embedded
 kobject) in their parent.
 
 As a kset contains a kobject within it, it should always be dynamically