Re: [PATCH 01/61] Rules on how to use sysfs in userspace programs

["Robert P. J. Day" <rpjday@mindspring.com>]

On Wed, 11 Jul 2007, Greg Kroah-Hartman wrote:

> From: Kay Sievers <kay.sievers@vrfy.org>
>
> Here's a document to help clear things up.
>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> ---
>  Documentation/sysfs-rules.txt |  166 +++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 166 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/sysfs-rules.txt
>
> diff --git a/Documentation/sysfs-rules.txt b/Documentation/sysfs-rules.txt
> new file mode 100644
> index 0000000..42861bb
> --- /dev/null
> +++ b/Documentation/sysfs-rules.txt
> @@ -0,0 +1,166 @@
> +Rules on how to access information in the Linux kernel sysfs
> +
> +The kernel exported sysfs exports internal kernel implementation-details
       kernel-exported                               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 can not provide a stable interface eighter,
                                                                      either
...

you might want to hold off on that patch for a few minutes.  :-)

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/