From: Thunder from the hill <thunder@lightweight.ods.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.5] Single linked lists for Linux, overly complicated v2
Date: Thu, 26 Sep 2002 13:43:41 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0209261337290.7827-100000@hawkeye.luckynet.adm> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209261628490.1837-100000@duckman.distro.conectiva>
Hi,
On Thu, 26 Sep 2002, Rik van Riel wrote:
> On Thu, 26 Sep 2002, Thunder from the hill wrote:
> In the case of slist_del() you HAVE to know it.
>
> Think about removing a single entry from the middle of
> the list ... the entries before and after need to stay
> on the list.
2 solutions without list head:
1.
#define slist_del_next(_entry_in) \
do { \
typeof(_entry_in) _entry = (_entry_in), \
_next = (_entry)->next; \
_entry->next = _next->next; \
_next->next = NULL; \
} while (0)
2. The previous entry points to the address that _entry has. If we
copy _entry somewhere else and overwrite the old _entry with
_entry->next, we made it without knowing the list topology. The
previous->next still points to the new _entry, things are fine.
My problem is just: where to put the old _entry? Anyway, since we're
talking about list entry deletion, we could copy it nowhere and just
overwrite it with _entry->next...
Details, details...
Thunder
--
assert(typeof((fool)->next) == typeof(fool)); /* wrong */
next prev parent reply other threads:[~2002-09-26 19:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020926142547.N13817@bitchcake.off.net>
2002-09-26 18:45 ` [PATCH][2.5] Single linked lists for Linux, overly complicated v2 Thunder from the hill
2002-09-26 19:29 ` Rik van Riel
2002-09-26 19:43 ` Thunder from the hill [this message]
2002-09-26 20:00 ` Rik van Riel
2002-09-26 20:10 ` Thunder from the hill
2002-09-26 21:13 ` Thunder from the hill
2002-09-26 21:19 ` Thunder from the hill
2002-09-27 0:57 ` Zach Brown
2002-09-27 20:08 ` Thunder from the hill
2002-09-27 20:39 ` Zach Brown
2002-09-27 20:52 ` Thunder from the hill
2002-09-28 9:45 ` Thunder from the hill
2002-09-30 19:37 ` Daniel Phillips
2002-09-30 20:04 ` Zach Brown
[not found] ` <E17w7N8-0005px-00@starship>
2002-09-30 20:50 ` Zach Brown
2002-10-01 16:05 ` Daniel Phillips
2002-09-26 19:49 ` David B. Stevens
[not found] <924963807@toto.iv>
2002-09-27 3:56 ` Peter Chubb
2002-09-27 7:27 ` Arnaldo Carvalho de Melo
2002-09-27 14:56 ` Thunder from the hill
2002-09-30 19:48 ` Daniel Phillips
2002-09-26 17:41 Lightweight Patch Manager
2002-09-26 17:53 ` Rik van Riel
2002-09-26 18:26 ` Thunder from the hill
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=Pine.LNX.4.44.0209261337290.7827-100000@hawkeye.luckynet.adm \
--to=thunder@lightweight.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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).