From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] struct list_node
Date: Mon, 11 Jun 2007 10:08:59 +1000 [thread overview]
Message-ID: <1181520539.16428.77.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.0.98.0706101317090.14121@woody.linux-foundation.org>
On Sun, 2007-06-10 at 13:19 -0700, Linus Torvalds wrote:
> And if you want a head, you really do want to use "hlist", since the head
> is smaller than a list entry (a single pointer rather than two).
No, now you're entirely missing the point.
The normal Linux lists are beautiful, and should be used! I share your
enthusiasm for them.
They could just use a little more type safety for the common case. That
is all.
Hope that clarifies,
Rusty.
next prev parent reply other threads:[~2007-06-11 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 5:11 Rusty Russell
2007-06-10 17:13 ` Randy Dunlap
2007-06-10 17:20 ` Linus Torvalds
2007-06-10 20:19 ` Linus Torvalds
2007-06-11 0:08 ` Rusty Russell [this message]
2007-06-11 0:02 ` Rusty Russell
2007-06-14 10:03 ` Jan Blunck
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=1181520539.16428.77.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®