All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maynard Johnson <maynardj@us.ibm.com>
To: Maynard Johnson <maynardj@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
	oprofile-list@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Cbe-oss-dev] [PATCH -- RFC]Add notification for active Cell SPU tasks	-- update #2
Date: Fri, 12 Jan 2007 16:00:11 -0600	[thread overview]
Message-ID: <45A804EB.9050505@us.ibm.com> (raw)
In-Reply-To: <45A2E615.5020900@us.ibm.com>

I've reworked this patch to resolve the problem I was seeing.  I will 
post the new patch in a separate, new posting with subject line of 
"[PATCH] Cell SPU task notification".

-Maynard

WARNING: multiple messages have this Message-ID (diff)
From: Maynard Johnson <maynardj@us.ibm.com>
To: Maynard Johnson <maynardj@us.ibm.com>
Cc: cbe-oss-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org, oprofile-list@lists.sourceforge.net
Subject: Re: [Cbe-oss-dev] [PATCH -- RFC]Add notification for active Cell SPU tasks	-- update #2
Date: Fri, 12 Jan 2007 16:00:11 -0600	[thread overview]
Message-ID: <45A804EB.9050505@us.ibm.com> (raw)
In-Reply-To: <45A2E615.5020900@us.ibm.com>

I've reworked this patch to resolve the problem I was seeing.  I will 
post the new patch in a separate, new posting with subject line of 
"[PATCH] Cell SPU task notification".

-Maynard


  reply	other threads:[~2007-01-12 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 15:51 [PATCH]Add notification for active Cell SPU tasks -- updated patch Maynard Johnson
2007-01-09  0:47 ` [Cbe-oss-dev] [PATCH -- RFC]Add notification for active Cell SPU tasks -- update #2 Maynard Johnson
2007-01-09  0:47   ` Maynard Johnson
2007-01-12 22:00   ` Maynard Johnson [this message]
2007-01-12 22:00     ` Maynard Johnson

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=45A804EB.9050505@us.ibm.com \
    --to=maynardj@us.ibm.com \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=oprofile-list@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.