git://ftp.safe.ca
/
safe
/
jmp
/
linux-2.6
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
vsprintf: pre-calculate final string length for later use
[safe/jmp/linux-2.6]
/
Documentation
/
kobject.txt
diff --git
a/Documentation/kobject.txt
b/Documentation/kobject.txt
index
bf3256e
..
c79ab99
100644
(file)
--- 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);
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.
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.
@@
-128,7
+132,7
@@
kobject_name():
const char *kobject_name(const struct kobject * kobj);
There is a helper function to both initialize and add the kobject to the
const char *kobject_name(const struct kobject * kobj);
There is a helper function to both initialize and add the kobject to the
-kernel at the same time, called su
p
prisingly enough kobject_init_and_add():
+kernel at the same time, called su
r
prisingly enough kobject_init_and_add():
int kobject_init_and_add(struct kobject *kobj, struct kobj_type *ktype,
struct kobject *parent, const char *fmt, ...);
int kobject_init_and_add(struct kobject *kobj, struct kobj_type *ktype,
struct kobject *parent, const char *fmt, ...);
@@
-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,
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 k
s
et have that kset (or, strictly, its embedded
kobject) in their parent.
As a kset contains a kobject within it, it should always be dynamically
kobject) in their parent.
As a kset contains a kobject within it, it should always be dynamically