From: Morten Helgesen <admin@nextframe.net>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: #include <linux/malloc.h> to #include <linux/slab.h> in the 2.2 tree.
Date: Tue, 27 Nov 2001 11:44:25 +0100 [thread overview]
Message-ID: <20011127114425.A119@sexything> (raw)
Hey there, Alan and the rest of you.
I was just wondering whether or not it would be a waste of time creating a patch with one goal in mind: substituting
references to linux/malloc.h with references to linux/slab.h throughout the 2.2 tree.
Inconsistency is a Bad Thing[tm], and since malloc.h now only includes slab.h, I feel that it is time for a major clean-up.
Any thoughts ?
== Morten
--
mvh
Morten Helgesen
UNIX System Administrator & C Developer
Nextframe AS, Horten, Norway
admin@nextframe.net / 93445641
http://www.nextframe.net
reply other threads:[~2001-11-27 10:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011127114425.A119@sexything \
--to=admin@nextframe.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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