linux-kernel - Re: [PATCH] cpuset and sched domains: sched_load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 5 Oct 2007 16:39:18 -0700
From:	Paul Jackson <pj@....com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	nickpiggin@...oo.com.au, randy.dunlap@...cle.com,
	menage@...gle.com, linux-kernel@...r.kernel.org, dino@...ibm.com,
	cpw@....com, mingo@...e.hu
Subject: Re: [PATCH] cpuset and sched domains: sched_load_balance flag fixes

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@....com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/