public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Paul Menage" <menage@google.com>
Cc: "Paul Jackson" <pj@sgi.com>,
	torvalds@linux-foundation.org, lizf@cn.fujitsu.com,
	"Hidetoshi Seto" <seto.hidetoshi@jp.fujitsu.com>,
	"Hiroyuki KAMEZAWA" <kamezawa.hiroyu@jp.fujitsu.com>,
	"Dimitri Sivanich" <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 18:03:26 -0700	[thread overview]
Message-ID: <20080506180326.f2f69dea.akpm@linux-foundation.org> (raw)
In-Reply-To: <6599ad830805061726n33f69552k756e8754387e4b8c@mail.gmail.com>

On Tue, 6 May 2008 17:26:22 -0700 "Paul Menage" <menage@google.com> wrote:

> On Tue, May 6, 2008 at 5:20 PM, Paul Jackson <pj@sgi.com> wrote:
> >
> >  I definitely agree with the above observations of Paul M.  I suspect
> >  that the patch might be missing the lines needed to -remove- the
> >  FILE_SCHED_RELAX_DOMAIN_LEVEL cases from the old style
> >  cpuset_common_file_read and cpuset_common_file_write switches.
> 
> Yes, it is - but I didn't have a tree with the relevant bits in it to
> remove, as far as I could see.

This whole fiasco was caused by unexpected changes magically appearing in
mainline late in the merge window.  All very predictable.

> >
> >   2) I didn't see any replies from Paul M in response to
> >     Andrews above request to "send us any needed fixup later
> >     in the week".
> >
> >         ==> Paul M or akpm - Is this fixup in the pipeline?
> 
> Not yet - I was waiting for 2.6.26-rc1-mm1 to come out. But I can send
> one against 2.6.26-rc1 directly if that helps.

I'm still crunching on backlog.  A fix against mainline would be great,
thanks.


  parent reply	other threads:[~2008-05-07  1:04 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 [this message]
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=20080506180326.f2f69dea.akpm@linux-foundation.org \
    --to=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=pj@sgi.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