From: David Woodhouse <dwmw2@infradead.org>
To: dalecki@evision.ag
Cc: Pavel Machek <pavel@suse.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: __get_free_pages but no get_free_pages?
Date: Fri, 16 Nov 2001 14:25:58 +0000 [thread overview]
Message-ID: <5431.1005920758@redhat.com> (raw)
In-Reply-To: <3BF4F6A6.10163203@evision-ventures.com>
In-Reply-To: <3BF4F6A6.10163203@evision-ventures.com> <20011115233528.A7496@elf.ucw.cz>
dalecki@evision-ventures.com said:
> That's purposedly so to discourage the usage of it, since this
> function should be considered as an "implementation detail" I think.
An implementation detail that should be hidden from generic code.
Like the fact that we use slabs for malloc?
--
dwmw2
prev parent reply other threads:[~2001-11-16 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 22:35 __get_free_pages but no get_free_pages? Pavel Machek
2001-11-16 11:21 ` Martin Dalecki
2001-11-16 14:25 ` David Woodhouse [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=5431.1005920758@redhat.com \
--to=dwmw2@infradead.org \
--cc=dalecki@evision.ag \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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