From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
torvalds@osdl.org, jbarnes@engr.sgi.com, colpatch@us.ibm.com,
nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: SMP Panic caused by [PATCH] sched: consolidate sched domains]
Date: Fri, 3 Sep 2004 15:22:12 -0700 [thread overview]
Message-ID: <20040903222212.GV3106@holomorphy.com> (raw)
In-Reply-To: <20040903145925.1e7aedd3.akpm@osdl.org>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
>> Could we get this in please? The current screw up in the scheduling
>> domain patch means that any architecture that actually hotplugs CPUs
>> will crash in find_busiest_group() ... and I notice this has just bitten
>> the z Series people...
On Fri, Sep 03, 2004 at 02:59:25PM -0700, Andrew Morton wrote:
> Have we yet seen anything which looks like a completed and tested patch?
This is the whole thing; the "other half" referred to a new hunk added to
the patch (identical to this one) posted in its entirety.
-- wli
next prev parent reply other threads:[~2004-09-03 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 21:21 [Fwd: Re: SMP Panic caused by [PATCH] sched: consolidate sched domains] James Bottomley
2004-09-03 21:59 ` Andrew Morton
2004-09-03 22:13 ` James Bottomley
2004-09-03 22:22 ` William Lee Irwin III [this message]
[not found] ` <20040903153434.15719192.akpm@osdl.org>
2004-09-03 22:45 ` [sched] fix sched_domains hotplug bootstrap ordering vs. cpu_online_map issue William Lee Irwin III
2004-09-04 1:57 ` Nick Piggin
2004-09-05 11:46 ` Ingo Molnar
2004-09-05 22:35 ` James Bottomley
2004-09-06 2:48 ` Nick Piggin
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=20040903222212.GV3106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@osdl.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