From: Tim Jansen <tim@tjansen.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC] proc fs extension for "one-value-per-file"
Date: Mon, 14 May 2001 20:59:33 +0200 [thread overview]
Message-ID: <01051420593300.00951@cookie> (raw)
The following patch extends the proc fs api as discussed in the thread "/proc
format" last month (http://marc.theaimsgroup.com/?t=98822545000007&w=2&r=1).
It adds the following features:
- dynamic directories. Enables you to use directories for enumerations,
similar to the per-process directories (/proc/<number>) or usbdevfs.
- context callbacks for directories. They can do things that are common for
all files in a directory, like locking, and are also used for dynamic
directories.
- special functions with context support for proc files that containing short
strings, integers or enums
These things give the proc filesystem the functionality that I need for the
Device Registry patch to replace the XML output with the one-value-per-file
approach. The api is documented in fs/proc/onevalue.c.
You can download the patch for 2.4.4 here (40 kB):
http://www.tjansen.de/devreg/proc_ov-2.4.4.diff
bye...
reply other threads:[~2001-05-14 19:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01051420593300.00951@cookie \
--to=tim@tjansen.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox