public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: bob.picco@hp.com
Cc: akpm@osdl.org, simon.derr@bull.net, linux-kernel@vger.kernel.org,
	bob.picco@hp.com
Subject: Re: [PATCH] cpuset - fix return without releasing semaphore
Date: Sat, 12 Nov 2005 11:26:28 -0800	[thread overview]
Message-ID: <20051112112628.22aaa314.pj@sgi.com> (raw)
In-Reply-To: <20051112022122.22085.45247.sendpatchset@localhost.localdomain>

> This was only compile tested.

I boot, function and stress tested it on an ia64 SN2 system.
As expected, works fine, just as it did before.

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

      parent reply	other threads:[~2005-11-12 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12  2:20 [PATCH] cpuset - fix return without releasing semaphore bob.picco
2005-11-12 18:17 ` Paul Jackson
2005-11-12 19:26 ` Paul Jackson [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=20051112112628.22aaa314.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=bob.picco@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon.derr@bull.net \
    /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