public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: afei@jhu.edu
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: The 2.4 /proc module change
Date: Thu, 03 May 2001 13:51:10 -0400	[thread overview]
Message-ID: <3AF19A8E.5E306079@mandrakesoft.com> (raw)
In-Reply-To: <Pine.GSO.4.05.10105031325030.13150-100000@aa.eps.jhu.edu>

afei@jhu.edu wrote:
> 
> In the old 2.x kernels, a /proc module registers itself through
> proc_register(&proc_root, &proc_self) and unregister itself through
> proc_unregister(&proc_root, inode)

Use create_proc[_read]_entry and remove_proc_entry instead... 
create_proc_read_entry was added in 2.3, but {create,remove}_proc_entry
should work in 2.2 also, iirc.

-- 
Jeff Garzik      | Game called on account of naked chick
Building 1024    |
MandrakeSoft     |

      reply	other threads:[~2001-05-03 17:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23  9:20 [patch] swap-speedup-2.4.3-A1, massive swapping speedup Ingo Molnar
2001-04-23 15:33 ` Rik van Riel
2001-04-23 16:05   ` [patch] swap-speedup-2.4.3-A2 Ingo Molnar
2001-04-23 17:16     ` giga ethernet/National Semiconductor dp83820 M. Osten
2001-04-23 17:17     ` [patch] swap-speedup-2.4.3-A2 Linus Torvalds
2001-04-23 16:54       ` Ingo Molnar
2001-04-24  5:44     ` [patch] swap-speedup-2.4.3-B3 Ingo Molnar
2001-04-24 16:38       ` Linus Torvalds
2001-04-25  2:28         ` Marcelo Tosatti
2001-04-23 16:53 ` [patch] swap-speedup-2.4.3-A1, massive swapping speedup Jonathan Morton
2001-04-23 17:10   ` Linus Torvalds
2001-04-23 22:13     ` Marcelo Tosatti
2001-05-03 17:36     ` The 2.4 /proc module change afei
2001-05-03 17:51       ` Jeff Garzik [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=3AF19A8E.5E306079@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=afei@jhu.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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