From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Brad Parker" <parker@citynetwireless.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: programming with /proc functions
Date: Fri, 5 Sep 2003 09:08:25 -0700 [thread overview]
Message-ID: <20030905090825.63bde24b.rddunlap@osdl.org> (raw)
In-Reply-To: <005401c37359$e6c30550$20f6d618@bp>
On Thu, 4 Sep 2003 22:00:44 -0500 "Brad Parker" <parker@citynetwireless.net> wrote:
| How can I find out what I need to change for a module (which creates a /proc
| entry) I wrote for 2.2 to work under 2.4, meaning, things like
| proc_register[_dynamic], proc_unregister etc. are gone now, how do I go
| about figuring out what all needs to be changed?
I don't recall a 2.2-to-2.4 porting guide. Anyone else?
There is a 2.4 /proc fs guide at
http://kernelnewbies.org/documents/kdoc/procfs-guide/lkprocfsguide.html
that may help you.
--
~Randy
prev parent reply other threads:[~2003-09-05 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 3:00 programming with /proc functions Brad Parker
2003-09-05 16:08 ` Randy.Dunlap [this message]
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=20030905090825.63bde24b.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parker@citynetwireless.net \
/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