linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: Andrew Morton <akpm@osdl.org>,
	Jes Sorensen <jes@trained-monkey.org>,
	linuxppc-embedded@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] genalloc != generic DEVICE memory allocator
Date: Fri, 23 Dec 2005 13:17:58 +0300	[thread overview]
Message-ID: <43ABCED6.2030008@varma-el.com> (raw)
In-Reply-To: <43ABAB69.4060703@intracom.gr>



Pantelis Antoniou wrote:
>>
> 
> [snip]
> 
>>
>> Agree, I couldn't see nothing better for a basement of generic dev.
>> alloc.
>>
>> So, it will be much better if it will be moved to lib/.
>>
>> Anyone have some more comments about subj. ?
>>
> 
> Sure, but the call has to be made be a core developer.
> 
> Andrew?

Pantelis, what did you think about renaming rheap.c and rh_xxx, to
something like dev_xxx, since, for example, rh_alloc overlapped with
__rh_alloc (__RegionHach__alloc) in the drivers/md/dm-raid1.c.


-- 
Regards
Andrey Volkov

  reply	other threads:[~2005-12-23 10:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 17:23 [RFC] genalloc != generic DEVICE memory allocator Andrey Volkov
2005-12-22  8:38 ` Pantelis Antoniou
2005-12-22 13:48   ` Andrey Volkov
2005-12-22 14:15     ` Pantelis Antoniou
2005-12-22 15:44       ` Andrey Volkov
2005-12-22 16:09         ` Pantelis Antoniou
     [not found] ` <43A9B2F1.8090402@246tNt.com>
2005-12-22 13:41   ` Andrey Volkov
2005-12-22 15:37 ` Jes Sorensen
2005-12-22 18:18   ` Andrey Volkov
2005-12-22 18:33     ` Pantelis Antoniou
2005-12-23  7:38       ` Andrey Volkov
2005-12-23  7:46         ` Pantelis Antoniou
2005-12-23 10:17           ` Andrey Volkov [this message]
2005-12-23 10:59     ` Jes Sorensen

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=43ABCED6.2030008@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=akpm@osdl.org \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=panto@intracom.gr \
    /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).