From: Adam Belay <ambx1@netscape.net>
To: mochel@osdl.org, rgooch@atnf.csiro.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] integrate driverfs and devfs (2.5.28)
Date: Mon, 29 Jul 2002 13:47:15 +0000 [thread overview]
Message-ID: <3D454763.5050903@netscape.net> (raw)
In-Reply-To: 3D445C2F.20603@netscape.net
Forgot to mention:
- the floppy driver was converted as an example
- adds a new file "dev" to each driverfs entry
- output is in the following format
MAJOR,MINOR PATH
- one line per each devfs entry during output
- to test try: #cat (driverfs)/root/sys/03?0/dev
assuming you have a floppy drive
- Applies cleanly to 2.5.29 as well
- If there's a demand for it I'll add the ability to unregister
individual devfs entries from driverfs
Cheers,
ambx1
ambx1@netscape.net wrote:
> This patch integrates driverfs and devfs. A summary is as follows:
> - create new interface directory and move interface.c
> * I intend to add more to this directory later
> - add devfs entry list
> - add devfs related functions
> - create devfs interface
> This patch is intended to be as non intrusive as possible. Therefore
> it doesn't modify devfs directly but instead creates a layer above it.
> This is due to the fact that if devfs was modified it would break
> every driver. Eventually we have to decide when and how to
> integrate it directly, This patch will provide the necessary
> infrastructure. Please Apply.
> cheers,
> Adam Belay
next prev parent reply other threads:[~2002-07-29 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 21:03 [PATCH] integrate driverfs and devfs (2.5.28) Adam Belay
2002-07-29 13:47 ` Adam Belay [this message]
2002-07-29 19:33 ` Patrick Mochel
2002-07-29 16:47 ` Adam Belay
2002-07-29 22:21 ` Patrick Mochel
2002-07-29 23:25 ` Oliver Neukum
2002-07-30 16:32 ` Patrick Mochel
2002-07-30 14:02 ` Adam Belay
2002-08-05 6:26 ` Rob Landley
2002-08-05 23:19 ` Greg KH
2002-08-05 23:51 ` Policy vs API (was Re: [PATCH] integrate driverfs and devfs (2.5.28)) Rob Landley
2002-08-06 16:34 ` Greg KH
2002-08-06 17:43 ` Patrick Mochel
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=3D454763.5050903@netscape.net \
--to=ambx1@netscape.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rgooch@atnf.csiro.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.