From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: [PATCH] for_each_zone / for_each_pgdat
Date: Mon, 15 Apr 2002 22:18:09 +0100 [thread overview]
Message-ID: <20020415221809.A22149@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44L.0204151755491.16531-100000@duckman.distro.conectiva> <Pine.LNX.4.33.0204151400200.13034-100000@penguin.transmeta.com>
On Mon, Apr 15, 2002 at 02:08:54PM -0700, Linus Torvalds wrote:
> Which requires the user to use something like
>
> for_each_zone(zone) {
> ...
> } end_zone;
>
> but doesn't need changing the double loop into a artificial single loop.
Bah, wli's version is so much nicer to use - in my eyes that justifies
the additional complexity in the macro.
next prev parent reply other threads:[~2002-04-15 21:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 15:49 Rik van Riel
2002-04-15 20:49 ` Linus Torvalds
2002-04-15 20:58 ` Rik van Riel
2002-04-15 21:08 ` Linus Torvalds
2002-04-15 21:17 ` Linus Torvalds
2002-04-15 23:20 ` William Lee Irwin III
2002-04-16 0:44 ` Andrea Arcangeli
2002-04-16 1:30 ` Mike Fedyk
2002-04-16 4:27 ` Rik van Riel
2002-04-16 13:36 ` Andrea Arcangeli
2002-04-16 13:44 ` Andrea Arcangeli
2002-04-16 16:39 ` Mike Fedyk
2002-04-16 14:00 ` Bill Davidsen
2002-04-16 18:19 ` Mike Fedyk
2002-04-16 4:22 ` Marcelo Tosatti
2002-04-16 14:50 ` Oliver Xymoron
2002-04-16 14:56 ` Rik van Riel
2002-04-16 15:26 ` Oliver Xymoron
2002-04-16 15:46 ` J.A. Magallon
2002-04-15 21:18 ` Christoph Hellwig [this message]
2002-04-15 21:47 ` Rik van Riel
2002-04-15 22:19 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 0:25 Rik van Riel
2002-04-18 9:41 ` Pavel Machek
2002-04-11 18:23 Rik van Riel
2002-04-11 18:54 ` Rik van Riel
2002-04-12 0:07 ` Rik van Riel
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=20020415221809.A22149@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--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
all inboxes | Powered by JetHome®