The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: chrisw@sous-sol.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuset: remove extra cpuset_zone_allowed check in __alloc_pages
Date: Tue, 23 May 2006 09:38:29 -0700	[thread overview]
Message-ID: <20060523093829.84c50ee5.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605230929070.9765@schroedinger.engr.sgi.com>

Christoph wrote:
> Simply removing my patch from mm will do the same.

I doubt it.

Looks to me like your patch went into Linus's tree on March 24, 2006:

    changeset:   23661:1541c55e5f8d
    user:        Christoph Lameter <clameter@engr.sgi.com>
    date:        Fri Mar 24 23:33:22 2006 +0800
    summary:     [PATCH] cpusets: only wakeup kswapd for zones in the current cpuset

If that's so, then only a reversing patch will suffice.  Linus does not
remove patches from his tree; he only adds more patches.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

      reply	other threads:[~2006-05-23 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 18:11 cpusets: only wakeup kswapd for zones in the current cpuset Christoph Lameter
2006-05-23  1:23 ` Paul Jackson
2006-05-23  1:59   ` Christoph Lameter
2006-05-23  2:22     ` Paul Jackson
2006-05-23  2:28       ` Christoph Lameter
2006-05-23  6:35         ` [PATCH] cpuset: remove extra cpuset_zone_allowed check in __alloc_pages Chris Wright
2006-05-23  6:35           ` Paul Jackson
2006-05-23 16:29           ` Christoph Lameter
2006-05-23 16:38             ` Paul Jackson [this message]

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=20060523093829.84c50ee5.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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