public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] for_each_zone / for_each_pgdat
Date: Tue, 16 Apr 2002 09:39:20 -0700	[thread overview]
Message-ID: <20020416163920.GB23513@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204151400200.13034-100000@penguin.transmeta.com> <Pine.LNX.4.33.0204151415110.15353-100000@penguin.transmeta.com> <20020415232058.GO21206@holomorphy.com> <20020416024458.H26561@dualathlon.random> <20020416013016.GA23513@matchmail.com> <20020416154418.B25328@dualathlon.random>

On Tue, Apr 16, 2002 at 03:44:18PM +0200, Andrea Arcangeli wrote:
> On Mon, Apr 15, 2002 at 06:30:16PM -0700, Mike Fedyk wrote:
> > under testing.  Also, Andrew found a problem with your locking changes when
> > he split up your patch, and at the time you were saying it is ready and
> > there were no bug reports against in...
> 
> btw, it was a problem only for ext3.
>

Right, I forgot to mention that.

> > Does this patch conflict in any way with your vm patches?  If not they
> > should be able to co-exist.
> 
> it will generate rejects, but that's not the problem. My point is that
> your same argument about merging in later kernels, stable kernel tree,
> could be applied to patches that makes no difference to users too.
> 

True.  Has Rik's cleanup already been merged into 2.5?

> Andrea
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2002-04-16 16:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 15:49 [PATCH] for_each_zone / for_each_pgdat 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 [this message]
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
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=20020416163920.GB23513@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=andrea@suse.de \
    --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