From: Dinakar Guniguntala <dino@in.ibm.com>
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Simon Derr <Simon.Derr@bull.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.12-rc4] cpuset rmdir scheduling while atomic fix
Date: Thu, 26 May 2005 20:03:15 +0530 [thread overview]
Message-ID: <20050526143315.GB7068@in.ibm.com> (raw)
In-Reply-To: <20050526124110.GB6496@in.ibm.com>
Earlier I wrote:
> Paul, This was the same problem that I had reported earlier
> and fixed as well
>
> See, Message Id: fa.c883kus.qjgijs@ifi.uio.no on google groups
>
> As far as I can see this has already been fixed and is in
> 2.6.12-rc5-mm1
Well not exactly the same problem as what you are seeing, but
the fix was the same. It should be fixed in rc5-mm1. I can send
a patch against 2.6.12-rc5 if you want.
-Dinakar
next prev parent reply other threads:[~2005-05-26 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 8:25 [PATCH 2.6.12-rc4] cpuset rmdir scheduling while atomic fix Paul Jackson
2005-05-26 12:41 ` Dinakar Guniguntala
2005-05-26 14:33 ` Dinakar Guniguntala [this message]
2005-05-26 18:26 ` 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=20050526143315.GB7068@in.ibm.com \
--to=dino@in.ibm.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--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