linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Removal of PG_marker scheme from 2.4.6-pre
Date: Sun, 1 Jul 2001 20:14:42 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0107012000440.7651-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107012358460.9312-100000@duckman.distro.conectiva>

Correction: I said -ac13 was bad, but ac13 was actually ok. It was ac14
that was the problem spot.

Also note how Alan happened to merge the MM patches in the reverse order
from the preX series: in the -ac series, Rik's page_launder() patch is in
-ac14, while my VM changes are merged in -ac15. In my series, it was the
other way around: mine went in in -pre2, while Rik went into -pre3. In
both cases, it's the page_launder() thing that triggers it.

And in the -ac tree, there wasn't any interaction with other patches at
all, and ac14 has the "pure" page_launder() patch that was reversed in
-pre7.

And to make doubly sure, Tim <tcm@nac.net> also tested out various
pre-kernels and unofficial combinations. Thanks.

			Linus

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2001-07-02  3:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-30 19:30 Marcelo Tosatti
2001-07-01  4:35 ` Linus Torvalds
2001-07-02  2:02 ` Rik van Riel
2001-07-02  2:47   ` Linus Torvalds
2001-07-02  2:59     ` Rik van Riel
2001-07-02  3:14       ` Linus Torvalds [this message]
2001-07-03 15:46   ` Marcelo Tosatti

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.33.0107012000440.7651-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --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