[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0705171920330.3231@yvahk01.tjqt.qr>
Date: Thu, 17 May 2007 19:26:07 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Jörn Engel <joern@...ybastard.org>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mtd@...ts.infradead.org, Albert Cahalan <acahalan@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
Pekka Enberg <penberg@...helsinki.fi>,
Greg KH <greg@...ah.com>, Ingo Oeser <ioe-lkml@...eria.de>
Subject: Re: [PATCH] LogFS take three
On May 16 2007 02:06, Jörn Engel wrote:
>
>> > +/* memtree.c */
>> > +void btree_init(struct btree_head *head);
>> > +void *btree_lookup(struct btree_head *head, long val);
>> > +int btree_insert(struct btree_head *head, long val, void *ptr);
>> > +int btree_remove(struct btree_head *head, long val);
>>
>> These names are too generic. If we later add a btree library: blam.
>
>My plan was to move this code to lib/ sooner or later. If you consider
>it useful in its current state, I can do it immediatly. And if someone
>else merged a superior btree library I'd happily remove mine and use the
>new one instead.
>
>Opinions?
Why would we need another btree, when there is lib/rbtree.c?
Or does yours do something fundamentally different?
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists