From 8ce01a1258829e05f40817898f4293b1863ea119 Mon Sep 17 00:00:00 2001 From: Nathan Lynch Date: Wed, 2 Jul 2008 10:21:30 -0700 Subject: [PATCH] --- yaml --- r: 104780 b: refs/heads/master c: 83c79b55f0d929a0dcf2b0d347cd1875afc06f21 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/sysfs-rules.txt | 5 ++--- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index cd7e5a0be9fa..fb191e3fe9b1 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 9505e6375640fc61d92d36c8e9f25a6a218f3f57 +refs/heads/master: 83c79b55f0d929a0dcf2b0d347cd1875afc06f21 diff --git a/trunk/Documentation/sysfs-rules.txt b/trunk/Documentation/sysfs-rules.txt index 80ef562160bb..6049a2a84dda 100644 --- a/trunk/Documentation/sysfs-rules.txt +++ b/trunk/Documentation/sysfs-rules.txt @@ -3,9 +3,8 @@ Rules on how to access information in the Linux kernel sysfs The kernel-exported sysfs exports internal kernel implementation details and depends on internal kernel structures and layout. It is agreed upon by the kernel developers that the Linux kernel does not provide a stable -internal API. As sysfs is a direct export of kernel internal -structures, the sysfs interface cannot provide a stable interface either; -it may always change along with internal kernel changes. +internal API. Therefore, there are aspects of the sysfs interface that +may not be stable across kernel releases. To minimize the risk of breaking users of sysfs, which are in most cases low-level userspace applications, with a new kernel release, the users