linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Matt Sealey <matt@genesi-usa.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: rh_init exported twice (rheap vs. dm-region_hash)
Date: Mon, 23 Jun 2008 07:38:23 -0500	[thread overview]
Message-ID: <485F993F.9060101@freescale.com> (raw)
In-Reply-To: <485F9806.1000408@genesi-usa.com>

Matt Sealey wrote:

> I was thinking of renaming the dm hash one to rh_hash_init() and then I
> thought, maybe rh_heap_init() is better. Then I thought, why have rh in
> both places, why not rename the entire API (rheap_ and rhash_) in both
> cases?

I'm okay with renaming the rh_xxx calls in rheap.c to rheap_xxx.  I also think 
renaming the rh_ calls to rhash is a good idea.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

      reply	other threads:[~2008-06-23 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 12:33 rh_init exported twice (rheap vs. dm-region_hash) Matt Sealey
2008-06-23 12:38 ` 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=485F993F.9060101@freescale.com \
    --to=timur@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.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).