public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: menage@google.com, torvalds@linux-foundation.org,
	lizf@cn.fujitsu.com, seto.hidetoshi@jp.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, sivanich@sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 125/311] Cpuset hardwall flag: switch cpusets to use the bulk cgroup_add_files() API
Date: Tue, 6 May 2008 20:44:07 -0500	[thread overview]
Message-ID: <20080506204407.96862779.pj@sgi.com> (raw)
In-Reply-To: <20080506180006.107b2dcd.akpm@linux-foundation.org>

> > 	==> akpm - what does todays 2.6.25-rc1-mm1-mmotm
> > 	    apply to?
> 
> 2.6.25-rc1.
> 
> <resyncs>
> 
> It _should_ be OK.  Please check?

mmotm works fine now ... probably would have worked fine
before, except for the brain damaged keyboard operator
who is sitting behind my computer monitor - curse him ;).

Thanks.

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

      reply	other threads:[~2008-05-07  1:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804290800.m3T80QFs009131@imap1.linux-foundation.org>
     [not found] ` <6599ad830804290329heea3c5fu7395b1ef71a87881@mail.gmail.com>
     [not found]   ` <20080429053804.6d083a7f.akpm@linux-foundation.org>
2008-05-07  0:20     ` [patch 125/311] Cpuset hardwall flag: switch cpusets to use the bulk cgroup_add_files() API Paul Jackson
2008-05-07  0:26       ` Paul Menage
2008-05-07  0:39         ` Paul Jackson
2008-05-07  1:03         ` Andrew Morton
2008-05-07  1:21           ` Paul Menage
2008-05-07  1:00       ` Andrew Morton
2008-05-07  1:44         ` 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=20080506204407.96862779.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.com \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=sivanich@sgi.com \
    --cc=torvalds@linux-foundation.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