All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Paul Menage" <menage@google.com>
Cc: akpm@linux-foundation.org, 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 19:39:31 -0500	[thread overview]
Message-ID: <20080506193931.3e009405.pj@sgi.com> (raw)
In-Reply-To: <6599ad830805061726n33f69552k756e8754387e4b8c@mail.gmail.com>

Paul M wrote:
> But I can send one against 2.6.26-rc1 directly if that helps.

At this point, whatever resolves this with the least amount of
additional effort and confusion on the parts of Linus, Andrew,
Seto-san and yourself seems best.  A few days one way or the
other don't matter, so far as I know.

-- 
                  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  0:39 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 [this message]
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

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=20080506193931.3e009405.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.