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: nickpiggin@yahoo.com.au, randy.dunlap@oracle.com,
	menage@google.com, linux-kernel@vger.kernel.org, dino@in.ibm.com,
	cpw@sgi.com, mingo@elte.hu
Subject: Re: [PATCH] cpuset and sched domains: sched_load_balance flag fixes
Date: Fri, 5 Oct 2007 16:39:18 -0700	[thread overview]
Message-ID: <20071005163918.46d40fed.pj@sgi.com> (raw)
In-Reply-To: <20071005161305.af27f452.akpm@linux-foundation.org>

Andrew wrote:
> I'm getting 100% rejects from this - probably whatever patch it is
> patching got lost or unrecognisably mangled.

Yup - so far as I can tell, you didn't pick up the base patch that
this current patch fixes.  So, no, I wouldn't expect this patch to
make any sense.

As I stated in this current patch in the diffstat section after the
'---' marker, this current patch applies to the base patch of Subject:

  [PATCH] cpuset and sched domains: sched_load_balance flag

You probably didn't pick up that base patch because Nick and I are
still haggling over it.  Well ... we've agreed, but I can't get the
scheduler to work as I thought Nick wanted, and I'm still waiting
to hear from Nick again.

==> So yeah - throw this current patch out.

Nick ... you there ?

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

  reply	other threads:[~2007-10-05 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 11:44 [PATCH] cpuset and sched domains: sched_load_balance flag fixes Paul Jackson
2007-10-05 23:13 ` Andrew Morton
2007-10-05 23:39   ` Paul Jackson [this message]
2007-10-06  5:53     ` Ingo Molnar
2007-10-06  6:01       ` Paul Jackson
2007-10-06  6:21         ` Ingo Molnar
2007-10-06  6:28           ` 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=20071005163918.46d40fed.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=cpw@sgi.com \
    --cc=dino@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=randy.dunlap@oracle.com \
    /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