From: Segher Boessenkool <segher@kernel•crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom•com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs•org>
Subject: Re: platform_ops.malloc() vs. realloc()
Date: Thu, 22 Feb 2007 11:31:49 +0100 [thread overview]
Message-ID: <dcd4ed49af66f0fb9bb0eb1e86823c54@kernel.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0702221112010.22848@pademelon.sonytel.be>
> | void * (*malloc)(u32 size);
> | void * (*realloc)(void *ptr, unsigned long size);
> Is there a specific reason why the size parameters of malloc() and
> realloc()
> differ in type?
There are good arguments to prefer either u32 or unsigned
long, so maybe the current situation is a compromise ;-P
Segher
prev parent reply other threads:[~2007-02-22 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 10:14 platform_ops.malloc() vs. realloc() Geert Uytterhoeven
2007-02-22 10:25 ` David Gibson
2007-02-22 10:31 ` Segher Boessenkool [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=dcd4ed49af66f0fb9bb0eb1e86823c54@kernel.crashing.org \
--to=segher@kernel$(echo .)crashing.org \
--cc=Geert.Uytterhoeven@sonycom$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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