From: Nigel Cunningham <ncunningham@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Nick's preempt nosched patch.
Date: Tue, 06 Dec 2005 15:23:53 +1000 [thread overview]
Message-ID: <1133846622.5501.20.camel@localhost> (raw)
In-Reply-To: <1133844903.5501.17.camel@localhost>
Hi again.
On Tue, 2005-12-06 at 15:02, Nigel Cunningham wrote:
> Hi.
>
> A while ago I had a problem with cpu hotplug failing to take down cpus
> due to preemption problems. Nick prepared a patch (included below) that
> fixed this, but it's not yet in mainline. The problem seems to have
> disappeared on my work desktop (so I thought it had been applied until I
> did a quick check), but a suspend2 user has just reported the problem
> again. Can look at applying this or something better in mainline,
> please?
Ah. I eat my words, having discovered that it has been merged since
2.6.14, which I was looking at earlier. Sorry for the noise.
Nigel
prev parent reply other threads:[~2005-12-06 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 5:02 Nick's preempt nosched patch Nigel Cunningham
2005-12-06 5:23 ` Nigel Cunningham [this message]
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=1133846622.5501.20.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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