From: Andreas Dilger <adilger@turbolabs.com>
To: David Dyck <dcd@tc.fluke.com>
Cc: linux-kernel@vger.kernel.org, R.E.Wolff@BitWizard.nl
Subject: Re: 2.5.3 missing <linux/malloc.h>
Date: Wed, 30 Jan 2002 15:44:34 -0700 [thread overview]
Message-ID: <20020130154434.L763@lynx.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.33.0201301239370.19671-100000@dd.tc.fluke.com>
In-Reply-To: <Pine.LNX.4.33.0201301239370.19671-100000@dd.tc.fluke.com>; from dcd@tc.fluke.com on Wed, Jan 30, 2002 at 02:28:28PM -0800
On Jan 30, 2002 14:28 -0800, David Dyck wrote:
> Haven't seen this posted yet, so I'm surprised to report that
> several 2.5.3 source files
>
> arch/arm/mach-clps711x/dma.c
> drivers/base/core.c
> drivers/base/fs.c
> drivers/video/neofb.c
>
>
> try to include linux/malloc.h
> but there is no file in the include directory by that name.
>
> I worked around the problem by copying an older linux/malloc.h:
>
> #ifndef _LINUX_MALLOC_H
> #define _LINUX_MALLOC_H
>
> #include <linux/slab.h>
> #endif /* _LINUX_MALLOC_H */
So, why not just change the above files to include <linux/slab.h>
instead?
> and I've noticed that many source files have
> #include <linux/slab.h> /* kmalloc(), kfree() */
> instead of trying to include linux/malloc.h
That's because they have been updated, and the other ones have not.
Don't ask me _why_ it was changed that way, but it was.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-30 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 22:28 David Dyck
2002-01-30 22:44 ` Andreas Dilger [this message]
2002-01-31 0:38 ` Jeff Garzik
2002-01-30 22:52 ` Ben Clifford
2002-02-01 13:19 ` Heinz J . Mauelshagen
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=20020130154434.L763@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=dcd@tc.fluke.com \
--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
all inboxes | Powered by JetHome®