From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: phillips@arcor.de, wli@holomorphy.com, rml@tech9.net,
rusty@rustcorp.com.au, torvalds@transmeta.com,
linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [TRIVIAL PATCH] Remove list_t infection.
Date: Tue, 3 Sep 2002 23:13:30 +0100 [thread overview]
Message-ID: <20020903231330.C6848@kushida.apsleyroad.org> (raw)
In-Reply-To: <20020902.030553.14354294.davem@redhat.com>; from davem@redhat.com on Mon, Sep 02, 2002 at 03:05:53AM -0700
David S. Miller wrote:
> A list node is markably different from "the list" itself.
>
> A "list" is the whole of all the nodes on the list, not just one
> of them.
Quite.
And that is why there should be _two_ types:
1. struct list
2. struct list_node
With these two types, `list_add' et al. can actually _check_ that you
got the arguments the right way around.
-- Jamie
next prev parent reply other threads:[~2002-09-03 22:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 5:23 Rusty Russell
2002-09-02 5:51 ` Robert Love
2002-09-02 6:02 ` William Lee Irwin III
2002-09-02 6:20 ` David S. Miller
2002-09-02 10:11 ` Daniel Phillips
2002-09-02 10:05 ` David S. Miller
2002-09-02 10:16 ` Daniel Phillips
2002-09-02 10:11 ` David S. Miller
2002-09-02 10:25 ` Daniel Phillips
2002-09-02 10:21 ` David S. Miller
2002-09-02 10:24 ` William Lee Irwin III
2002-09-03 22:13 ` Jamie Lokier [this message]
2002-09-03 23:14 ` Linus Torvalds
2002-09-04 0:41 ` Rusty Russell
2002-09-04 1:52 ` Daniel Phillips
2002-09-04 2:26 ` Linus Torvalds
2002-09-04 2:44 ` Rusty Russell
2002-09-04 14:36 ` J.A. Magallon
2002-09-04 6:11 ` Thunder from the hill
2002-09-02 6:23 ` Neil Brown
2002-09-01 20:45 ` Nick Piggin
2002-09-02 6:27 ` William Lee Irwin III
2002-09-02 10:07 ` Daniel Phillips
2002-09-02 10:05 ` Daniel Phillips
2002-09-02 6:17 ` Rusty Russell
2002-09-06 9:28 ` Dan Aloni
2002-09-06 14:35 ` Robert Love
2002-09-09 5:57 ` Rusty Russell
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=20020903231330.C6848@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=akpm@zip.com.au \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=rml@tech9.net \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.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
Powered by JetHome