From: Timur Tabi <timur@freescale.com>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Why do the rh_alloc functions return a pointer?
Date: Thu, 15 Feb 2007 14:34:23 -0600 [thread overview]
Message-ID: <45D4C3CF.9080800@freescale.com> (raw)
In-Reply-To: <45D4C2CB.2080703@246tNt.com>
Sylvain Munaut wrote:
> I talked about it with Panto on IRC a few days ago.
>
> And he agrees that the function could be changed to user "unsigned long"
> instead of "void *".
Well, if there is a consensus that this should be changed, then I'll make the patch.
However, since the function prototype for all architectures is in
include/asm-ppc/rheap.h, I'll need to change powerpc and ppc in the same patch,
otherwise one of the two will break.
--
Timur Tabi
Linux Kernel Developer @ Freescale
prev parent reply other threads:[~2007-02-15 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 19:29 Why do the rh_alloc functions return a pointer? Timur Tabi
2007-02-15 20:30 ` Sylvain Munaut
2007-02-15 20:34 ` Timur Tabi [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=45D4C3CF.9080800@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=tnt@246tNt.com \
/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;
as well as URLs for NNTP newsgroup(s).