aboutsummaryrefslogtreecommitdiffstats
path: root/lib/kobject_uevent.c
diff options
context:
space:
mode:
authorNathan Lynch <ntl@pobox.com>2008-07-02 13:21:30 -0400
committerGreg Kroah-Hartman <gregkh@suse.de>2008-07-22 00:54:59 -0400
commit83c79b55f0d929a0dcf2b0d347cd1875afc06f21 (patch)
tree618ba5db8c9c78a96aadd39997848b8ec45f90cf /lib/kobject_uevent.c
parent9505e6375640fc61d92d36c8e9f25a6a218f3f57 (diff)
sysfs-rules.txt: reword API stability statement
The first paragraph of this document implies that user space developers shouldn't use sysfs at all, but then it goes on to describe rules that developers should follow when accessing sysfs. Not only is this somewhat self-contradictory, it has been shown to discourage developers from using established sysfs interfaces. A note of caution is more appropriate than a blanket "sysfs will never be stable" assertion. Signed-off-by: Nathan Lynch <ntl@pobox.com> Cc: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'lib/kobject_uevent.c')
0 files changed, 0 insertions, 0 deletions