From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] type safe list
Date: Fri, 22 Jul 2005 20:08:35 +0400 [thread overview]
Message-ID: <42E11A03.6030400@namesys.com> (raw)
In-Reply-To: <20050722144153.GA17220@infradead.org>
Hello
Christoph Hellwig wrote:
> On Fri, Jul 22, 2005 at 05:58:56PM +0400, Vladimir V. Saveliev wrote:
>
>>Hello
>>
>>This is implementaion of circular doubly linked parametrized list.
>>It is similar to the list implementation in include/linux/list.h
>>but it also provides type safety which allows to detect some of list
>>manipulating
>>mistakes as soon as they happen.
>
>
> This looks like an ugly solution in search of a problem. Just use
> normal list.h list and get rid of this mess.
>
ok.
We have also type safe hash chain implementation.
I guess it also does not have a chance to get in?
prev parent reply other threads:[~2005-07-22 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 13:58 [RFC][PATCH] type safe list Vladimir V. Saveliev
2005-07-22 14:41 ` Christoph Hellwig
2005-07-22 16:08 ` Vladimir V. Saveliev [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=42E11A03.6030400@namesys.com \
--to=vs@namesys.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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