From: Christoph Hellwig <hch@ns.caldera.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-mm@kvack.org
Subject: Re: MM docs...
Date: Sat, 3 Mar 2001 13:12:44 +0100 [thread overview]
Message-ID: <20010303131244.A15788@caldera.de> (raw)
In-Reply-To: <3AA046D4.B7EC6999@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Fri, Mar 02, 2001 at 08:20:20PM -0500
On Fri, Mar 02, 2001 at 08:20:20PM -0500, Jeff Garzik wrote:
> Is there any chance that some knowledgeable people could write docs for
> the public functions in 2.4's linux/mm directory?
>
> I'm gonna finish up documenting kernel/*, drivers/pci* and a few drivers
> in drivers/net soon. mm/* is a hole in my knowledge, though, so I need
> to solicit for volunteers.
>
> It would be nice to silence the people complaining about the kernel's
> lack of internal docs. :)
I'm currently writing some documentation - it should end up as one chapter
in Tigran's lki.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2001-03-03 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 1:20 Jeff Garzik
2001-03-03 12:12 ` Christoph Hellwig [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=20010303131244.A15788@caldera.de \
--to=hch@ns.caldera.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-mm@kvack.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